Intelligent Distributed Industrial Facility Safety System

ABSTRACT

Provided are systems and methods for intelligent distributed industrial facility safety systems. In some embodiments an industrial facility safety system includes remote sensing devices (RSDs) disposed throughout an industrial facility, and a facility safety control system (FSCS) adapted to collect safety data from the RSDs, determine current conditions of the industrial facility based on the safety data collected, determine that an alert condition exists based on the current conditions determined, identify an alert associated with the alert condition, generate the alert for presentation to personnel in the industrial facility, monitor a response to the presentation of the alert, and dynamically adjust an alert level for the alert condition based on the response.

FIELD

Embodiments relate generally to industrial safety and more particularlyto distributed industrial facility safety systems employing remotesensing devices and intelligent facility safety control systems.

BACKGROUND

Employee health and safety continues to be an area of great importanceto employers. Safety concerns are especially heightened for industrialfacilities (often referred to as “industrial worksites”, “industrialplants” or simply “plants”). Industrial facilities include, for example,oil and gas plants, power plants, and the like. Industrial facilitiescan be complex systems that include large machinery, electrical systems,flow control systems, and the like. Large machinery can include, forexample, turbomachinery, such as turbines, generators and compressorswith components rotating at extremely high rates. Electrical systems caninclude, for example, power systems that generate, regulate andtransport high-voltage and high-current electrical power. Flow controlsystems can include, for example, flow control mechanisms, such asvalves, pressure vessels and pipes that regulate the flow of substances,such as oil and natural gas, at varying temperatures and pressures.Given their complexity, industrial facilities typically employ safetydevices and safety procedures to minimize the risk of safety incidents,such as physical injuries to persons, damage to the environment anddamage to the industrial facility itself.

An industrial facility often employs a process control system (PCS) andan industrial safety system (ISS). These systems are normally integratedwith one another and are often referred to collectively as an integratedcontrol and safety system (ICSS). The PCS typically monitors andcontrols the operations of the industrial facility systems to executeday-to-day operations of the facility, such as the processing of oil andnatural gas. The ISS typically oversees the safety of the industrialfacility, such as monitoring physical systems and taking actions toprotect persons, the industrial facility systems and the environment.These actions can include, for example, activating safety systems,deactivating malfunctioning equipment, issuing alerts and the like.

SUMMARY

Applicants have recognized that existing integrated control and safetysystems (ICSSs) and associated industrial safety systems (ISSs)generally rely on static sensing systems and predefined responses. Forexample, existing ISSs often rely on a centralized controller monitoringa set number of fixed sensors disposed throughout an industrial facility(e.g., sensors disposed on components of turbomachinery, electricalsystems and/or flow control systems), and implementing a predefinedresponse when one or more of the sensors indicates an safety hazard(e.g., a facility-wide shut-down when one or more of the sensors reportsmeasurements outside of acceptable operating ranges). Although this typeof safety monitoring can be successful in recognizing and resolvingcertain safety issues, it can be relatively inflexible, non-robust,and/or inefficient and/or ineffective under certain conditions. Withregard to being inflexible, fixed sensors may not provide a suitableamount of coverage to more important areas of a facility. For example,sensors distributed throughout a facility, in different locations, mayprovide a relatively balanced coverage even when a large portion offacility personnel are located in certain areas of the facility, andthus it would be beneficial to have a heightened level of monitoring inthose areas. In such a configuration, it may not be practical torelocate the fixed sensors as personnel migrate throughout the facility.With regard to being non-robust, the sensors often rely on directcommunication with a centralized controller and thus monitoring of anarea may not be possible if one or more sensors in the area losecommunication with the centralized controller. This can lead to gaps inmonitoring that can result in catastrophic consequences if an alertcondition goes undetected due to the lack of communication. With regardto inefficient or ineffective responses, existing ISSs may over estimateor underestimate the nature of an event, and may provide a response thatis too broad or limited to be effective and efficient. For example, ifthe fixed sensors are unable to pinpoint the location or migration of anevent, such as a gas leak, across a facility, the ISS may implementbroadly sweeping remedial actions, such as shutting down a majority orall plant operations, including equipment and processes that are not atrisk or that may otherwise be helpful in remediating the issue. As afurther example, if fixed leak detection sensors provide only partialcoverage of an area, it may be impossible to determine a preciselocation of a gas leak and how the gas is migrating through thefacility, resulting in the ISS issuing a facility-wide alert, withoutbeing able to provide specifics of the most critical areas for personnelto evacuate and avoid, or failing to issue an alert for an area affectedby the gas leak. This can be especially critical for situations in whichpersonnel need to circumvent an area, for example, to avoid exposure toa leaked toxic substance.

Recognizing these and other shortcomings of existing ISSs, Applicantshave developed intelligent industrial facility safety systems employingremote sensing devices. In some embodiments an industrial facilityincludes an industrial safety system (“ISS”) and one or more industrialfacility devices (“facility equipment”). The ISS can include a facilitysafety control system (“FSCS”) and one or more remote sensing devices(“RSDs”). In some embodiments, the RSDs include fixed-facility RSDs (or“fixed RSDs”) and/or mobile-personal RSDs (or “mobile RSDs”) that aredistributed throughout the industrial facility. A fixed RSD can includea RSD that remains stationary, such as, a RSD that is affixed tostationary facility equipment, such as a turbine, a generator, acompressor, a pump, a pressure vessel, and/or a pipe, or otherwiseprovided in relatively stationary position, such as attached to a pole,scaffolding and/or another stationary structure of the facility. Amobile RSD can include a RSD that is portable, such as a personal RSDthat is carried by or otherwise attached to a person (e.g., a personworking in the facility) or mobile device (e.g., a robot and/or drone)that moves throughout the facility. This can facilitate the personalRSDs moving throughout the facility to monitor conditions in areas ofthe facility where persons are located.

In some embodiments, a RSD includes a sensing unit, a processing unit,memory, a communications unit, and/or an alert unit. The sensing unitcan include one more sensors for sensing various characteristics of theenvironment surrounding the RSD, including characteristics of a personor a device (e.g., a piece of facility equipment and/or a mobile device)the RSD is attached to or is otherwise associated with. The sensors caninclude, for example, temperature sensors, flowrate sensors, pressuresensors, vibration sensors, gas detection sensors, acoustic sensors(e.g., microphones), and/or location sensors. The alert unit can includea device for presenting alerts audibly, visually, and/or in a tactilemanner. For example, the alert unit may include a speaker for audiblybroadcasting alerts, a display screen or lights for visually displayingalerts, and/or a vibration mechanism for providing a tactile sensationto communicate an alert. Corresponding alerts can also be provided, forexample, by way of external alert devices, such as displays or speakerslocated throughout the facility.

As described, the RSDs and the FSCS can be configured in differentcommunication schemes, such as standalone, mesh, distributed anddistributed-mesh configurations. The different communication schemes maysupport the robust and efficient exchange of safety information (e.g.,sensed safety data and alerts) between RSDs and/or the FSCS. Alerts canbe presented in various formats to communicate varying types ofinformation. For example, alerts can presented with varying combinationsof lights, sirens and instructions to communicate alert content topersons in the facility. Alert content can include various types ofcontent to be communicated to persons in the facility, such as statusinformation, suggested actions, or instructions for taking actions. TheRSDs can include modular devices that enable various modular sensormodules to be installed therein, thereby enabling on-demand installationof sensors. The ISS may employ intelligence to monitor and learncharacteristics of the facility and/or persons, and adapt alerts and/orother operations to the learned characteristics.

Provided in some embodiments is an industrial facility safety system,including: a plurality of RSDs disposed throughout an industrialfacility; and a FSCS adapted to: collect safety data from the pluralityof RSDs; determine current conditions of the industrial facility basedon the safety data collected; determine that an alert condition existsbased on the current conditions determined; identify a second levelalert associated with the alert condition; generate the second levelalert for presentation to personnel in the industrial facility; monitora response to presentation of the second level alert, the responseindicating whether the second level alert is too low of a priority, toohigh of a priority, or of an appropriate priority for the alertcondition; in response to determining that the response indicates thatthe second level alert is too low of a priority for the alert condition:incrementing a too low count associated with the alert condition and thesecond level alert; determining whether the too low count associatedwith the alert condition and the second level alert exceeds a too lowcount threshold; and in response to determining that the too low countassociated with the alert condition and the second level alert exceedsthe too low count threshold, associating a third level alert with thealert condition, the third level alert being of higher priority than thesecond level alert; and in response to determining that the responseindicates that the second level alert is too high of a priority for thealert condition: incrementing a too high count associated with the alertcondition and the second level alert; determining whether the too highcount associated with the alert condition and the second level alertexceeds a too high count threshold; in response to determining that thetoo high count associated with the alert condition and the second levelalert exceeds the too high count threshold, associating a first levelalert with the alert condition, the first level alert being of lowerpriority than the second level alert.

In some embodiments, the FSCS is further adapted to, in response todetermining the response indicates that the second level alert is of anappropriate priority for the alert condition, set the too high countassociated with the alert condition and the second level alert to zero.In certain embodiments, the FSCS is further adapted to: collect secondsafety data from the plurality of RSDs; determine second currentconditions of the industrial facility based on the second safety datacollected; determine that the alert condition exists based on the secondcurrent conditions determined; identify an alert currently associatedwith the alert condition; and generate the alert currently associatedwith the alert condition for presentation to personnel in the industrialfacility. In some embodiments, the alert currently associated with thealert condition includes one of the first level alert, the second levelalert and the third level alert. In certain embodiments, the first levelalert includes an alert adapted to be presented by a first subset of theplurality of RSDs that are associated with the alert condition, thesecond level alert includes an alert adapted to be presented in one ormore regions of the industrial facility that are associated with thealert condition, and the third level alert includes a facility widealert adapted to be presented in all regions of the industrial facility.In some embodiments, the FSCS is further adapted to: determine a zone ofinterest within the industrial facility based on the current conditionsof the industrial facility; collect third safety data from the pluralityof RSDs; determine third current conditions of the industrial facilitybased on the third safety data collected; and adjust the zone ofinterest based on the third current conditions of the industrialfacility. In certain embodiments, the FSCS is further adapted to:determine a sensor module associated with the adjusted zone of interest;determine one or more RSDs located in the adjusted zone of interest; andsend, to the one or more RSDs located in the adjusted zone of interest,an alert to install the sensor module in the one or more RSDs. In someembodiments, the FSCS is further adapted to: determine a sensing stateassociated with the adjusted zone of interest; determine one or moreRSDs located in the adjusted zone of interest; and command the one ormore RSDs located in the adjusted zone of interest to operate in thesensing state.

Provided in some embodiments is a method of industrial facility safetymonitoring. The method including: collecting, by a FSCS, first safetydata from a plurality of RSDs disposed throughout an industrialfacility; determining, by the FSCS, first current conditions of theindustrial facility based on the safety data collected; determining, bythe FSCS, that an alert condition exists based on the first currentconditions determined; identifying, by the FSCS, a first alertassociated with the alert condition; generating, by the FSCS, the firstalert for presentation to personnel in the industrial facility;monitoring, by the FSCS, a response to presentation of the first alert,the response indicating whether the first alert is too low of apriority, too high of a priority, or of an appropriate priority for thealert condition; in response to the FSCS determining that the responseindicates that the first alert is too high of a priority for the alertcondition, the FSCS: incrementing a too high count associated with thealert condition and the first alert; determining that the too high countassociated with the alert condition and the first alert exceeds a toohigh count threshold; in response to determining that the too high countassociated with the alert condition and the first alert exceeds the toohigh count threshold, associating a second alert with the alertcondition, the second alert being of lower priority than the firstalert.

In some embodiments, the method further includes: collecting, by theFSCS, second safety data from the plurality of RSDs; determining, by theFSCS, second current conditions of the industrial facility based on thesecond safety data collected; determining, by the FSCS, that the alertcondition exists based on the second current conditions determined;identifying, by the FSCS, the second alert currently associated with thealert condition; and generating, by the FSCS, the second alert currentlyassociated with the alert condition for presentation to the personnel inthe industrial facility. In certain embodiments, the method furtherincludes: collecting, by the FSCS, third safety data from the pluralityof RSDs; determining, by the FSCS, third current conditions of theindustrial facility based on the third safety data collected;determining, by the FSCS, that the alert condition exists based on thethird current conditions determined; identifying, by the FSCS, a thirdalert currently associated with the alert condition; generating, by theFSCS, the third alert currently associated with the alert condition forpresentation to the personnel in the industrial facility; monitoring, bythe FSCS, a response to presentation of the third alert, the responseindicating whether the third alert is too low of a priority, too high ofa priority, or of an appropriate priority for the alert condition; inresponse to the FSCS determining that the response indicates that thethird alert is too low of a priority for the alert condition, the FSCS:incrementing a too low count associated with the alert condition and thethird alert; determining that the too low count associated with thealert condition and the third alert exceeds a too low count threshold;and in response to determining that the too low count associated withthe alert condition and the third alert exceeds the too low countthreshold, associating a fourth alert with the alert condition, thefourth alert being of higher priority than the third alert. In someembodiments, the method further includes: collecting, by the FSCS,fourth safety data from the plurality of RSDs; determining, by the FSCS,fourth current conditions of the industrial facility based on the fourthsafety data collected; determining, by the FSCS, that the alertcondition exists based on the fourth current conditions determined;identifying, by the FSCS, a fifth alert currently associated with thealert condition; generating, by the FSCS, the fifth alert currentlyassociated with the alert condition for presentation to the personnel inthe industrial facility; monitoring, by the FSCS, a response topresentation of the fifth alert, the response indicating whether thefifth alert is too low of a priority, too high of a priority, or of anappropriate priority for the alert condition; and in response to theFSCS determining the response indicates that fifth alert is of anappropriate priority for the alert condition, the FSCS setting a toohigh count associated with the alert condition and the fifth alert tozero. In certain embodiments, the second alert includes an alertpresented by a first subset of the plurality of RSDs that are associatedwith the alert condition, and the first alert includes an alertpresented in one or more regions of the industrial facility that areassociated with the alert condition or a facility wide alert presentedin all regions of the industrial facility. In some embodiments, themethod further includes: determining, by the FSCS, a zone of interestwithin the industrial facility based on the current conditions of theindustrial facility; collecting, by the FSCS, fifth safety data from theplurality of RSDs; determining, by the FSCS, fifth current conditions ofthe industrial facility based on the fifth safety data collected; andadjusting, by the FSCS, the zone of interest based on the fifth currentconditions of the industrial facility. In some embodiments, the methodfurther includes: determining, by the FSCS, a sensor module associatedwith the adjusted zone of interest; determining, by the FSCS, one ormore RSDs located in the adjusted zone of interest; and sending, by theFSCS to the one or more RSDs located in the adjusted zone of interest,an alert to install the sensor module in the one or more RSDs. In someembodiments, the method further includes: determining, by the FSCS, asensing state associated with the adjusted zone of interest;determining, by the FSCS, one or more RSDs located in the adjusted zoneof interest; and commanding, by the FSCS, the one or more RSDs locatedin the adjusted zone of interest to operate in the sensing state.

Provided in some embodiments is a non-transitory computer readablestorage medium including program instructions stored thereon that areexecutable by a processor to cause the following operations ofindustrial facility safety monitoring: collecting, by a FSCS, safetydata from a plurality of RSDs disposed throughout an industrialfacility; determining, by the FSCS, current conditions of the industrialfacility based on the safety data collected; determining, by the FSCS,that an alert condition exists based on the current conditionsdetermined; identifying, by the FSCS, a second level alert associatedwith the alert condition; generating, by the FSCS, the second levelalert for presentation to personnel in the industrial facility;monitoring, by the FSCS, a response to presentation of the second levelalert, the response indicating whether the second level alert is too lowof a priority, too high of a priority, or of an appropriate priority forthe alert condition; in response to determining that the responseindicates that the second level alert is too low of a priority for thealert condition: incrementing a too low count associated with the alertcondition and the second level alert; determining whether the too lowcount associated with the alert condition and the second level alertexceeds a too low count threshold; and in response to determining thatthe too low count associated with the alert condition and the secondlevel alert exceeds the too low count threshold, associating a thirdlevel alert with the alert condition, the third level alert being ofhigher priority than the second level alert; and in response todetermining that the response indicates that the second level alert istoo high of a priority for the alert condition: incrementing a too highcount associated with the alert condition and the second level alert;determining whether the too high count associated with the alertcondition and the second level alert exceeds a too high count threshold;and in response to determining that the too high count associated withthe alert condition and the second level alert exceeds the too highcount threshold, associating a first level alert with the alertcondition, the first level alert being of lower priority than the secondlevel alert.

In some embodiments, the operations further include: in response todetermining the response indicates that the second level alert is of anappropriate priority for the alert condition, set the too high countassociated with the alert condition and the second level alert to zero.In some embodiments, the operations further include: collecting secondsafety data from the plurality of RSDs; determining second currentconditions of the industrial facility based on the second safety datacollected; determining that the alert condition exists based on thesecond current conditions determined; identifying an alert currentlyassociated with the alert condition; and generating the alert currentlyassociated with the alert condition for presentation to personnel in theindustrial facility. In some embodiments, the alert currently associatedwith the alert condition includes one of the first level alert, thesecond level alert and the third level alert. In some embodiments, thefirst level alert includes an alert adapted to be presented by a firstsubset of the plurality of RSDs that are associated with the alertcondition, the second level alert includes an alert adapted to bepresented in one or more regions of the industrial facility that areassociated with the alert condition, and the third level alert includesa facility wide alert adapted to be presented in all regions of theindustrial facility. In some embodiments, the operations furtherinclude: determining a zone of interest within the industrial facilitybased on the current conditions of the industrial facility; collectingthird safety data from the plurality of RSDs; determining third currentconditions of the industrial facility based on the third safety datacollected; and adjusting the zone of interest based on the secondcurrent conditions of the industrial facility. In some embodiments, theoperations further include: determining a sensor module associated withthe adjusted zone of interest; determining one or more RSDs located inthe adjusted zone of interest; and sending, to the one or more RSDslocated in the adjusted zone of interest, an alert to install the sensormodule in the one or more RSDs. In some embodiments, the operationsfurther include: determining a sensing state associated with theadjusted zone of interest; determining one or more RSDs located in theadjusted zone of interest; and commanding the one or more RSDs locatedin the adjusted zone of interest to operate in the sensing state.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram that illustrates an industrial facilityenvironment in accordance with one or more embodiments.

FIG. 2A is a diagram that illustrates remote sensing devices (RSDs) ofan industrial facility operating in a standalone configuration inaccordance with one or more embodiments.

FIG. 2B is a diagram that illustrates RSDs of an industrial facilityoperating in a mesh configuration in accordance with one or moreembodiments.

FIG. 2C is a diagram that illustrates RSDs of an industrial facilityoperating in a distributed configuration in accordance with one or moreembodiments.

FIG. 2D is a diagram that illustrates RSDs of an industrial facilityoperating in a distributed-mesh configuration in accordance with one ormore embodiments.

FIG. 3A is a diagram that illustrates a method of operating a remotesensing device (RSD) in a standalone configuration in accordance withone or more embodiments.

FIG. 3B is a diagram that illustrates a method of operating a RSD in amesh configuration in accordance with one or more embodiments.

FIG. 3C is a diagram that illustrates a method of operating a RSD in adistributed configuration in accordance with one or more embodiments.

FIG. 3D is a diagram that illustrates a method of operating a RSD in adistributed-mesh configuration in accordance with one or moreembodiments.

FIG. 4 is a diagram that illustrates a RSD employing a modular sensingunit in accordance with one or more embodiments.

FIG. 5 is a block diagram that illustrates a method of operating anindustrial safety system (ISS) employing modular RSDs in accordance withone or more embodiments.

FIG. 6 is a block diagram that illustrates a method of dynamicallycategorizing conditions based on responses to corresponding alerts inaccordance with one or more embodiments.

FIG. 7 is a block diagram that illustrates a method of dynamicallymodifying zones of interest within an industrial facility in accordancewith one or more embodiments.

FIG. 8 is a diagram that illustrates an example computer system inaccordance with one or more embodiments.

While this disclosure is susceptible to various modifications andalternative forms, specific embodiments are shown by way of example inthe drawings and will be described in detail. The drawings may not be toscale. It should be understood that the drawings and the detaileddescriptions are not intended to limit the disclosure to the particularform disclosed, but are intended to disclose modifications, equivalents,and alternatives falling within the spirit and scope of the presentdisclosure as defined by the claims.

DETAILED DESCRIPTION

Described are embodiments of systems and methods for intelligentindustrial facility safety systems employing remote sensing devices. Insome embodiments an industrial facility includes an industrial safetysystem (“ISS”) and one or more industrial facility devices (“facilityequipment”). The ISS can include a facility safety control system(“FSCS”) and one or more remote sensing devices (“RSDs”). In someembodiments, the RSDs include fixed-facility RSDs (or “fixed RSDs”)and/or mobile-personal RSDs (or “mobile RSDs”) that are distributedthroughout the industrial facility. A fixed RSD can include a RSD thatremains stationary, such as, a RSD that is affixed to stationaryfacility equipment, such as a turbine, a generator, a compressor, apump, a pressure vessel, and/or a pipe, or otherwise provided inrelatively stationary position, such as attached to a pole, scaffoldingand/or another stationary structure of the facility. A mobile RSD caninclude a RSD that is portable, such as a personal RSD that is carriedby or otherwise attached to a person (e.g., a person working in thefacility) or mobile device (e.g., a robot and/or drone) that movesthroughout the facility. This can facilitate the personal RSDs movingthroughout the facility to monitor conditions in areas of the facilitywhere persons are located.

In some embodiments, a RSD includes a sensing unit, a processing unit,memory, a communications unit, and/or an alert unit. The sensing unitcan include one more sensors for sensing various characteristics of theenvironment surrounding the RSD, including characteristics of a personor a device (e.g., a piece of facility equipment and/or a mobile device)the RSD is attached to or is otherwise associated with. The sensors caninclude, for example, temperature sensors, flowrate sensors, pressuresensors, vibration sensors, gas detection sensors, microphones, and/orlocation sensors. The alert unit can include a device for presentingalerts audibly, visually, and/or in a tactile manner. For example, thealert unit may include a speaker for audibly broadcasting alerts, adisplay screen or lights for visually displaying alerts, and/or avibration mechanism for providing a tactile sensation to communicate analert. Corresponding alerts can also be provided, for example, by way ofexternal alert devices, such as displays or speakers located throughoutthe facility.

As described, the RSDs and the FSCS can be configured in differentcommunication schemes, such as standalone, mesh, distributed anddistributed-mesh configurations. The different communication schemes maysupport the robust and efficient exchange of safety information (e.g.,sensed safety data and alerts) between RSDs and/or the FSCS. Alerts canbe presented in various formats to communicate varying types ofinformation. For example, alerts can presented with varying combinationsof lights, sirens and instructions to communicate alert content topersons in the facility. Alert content can include various types ofcontent to be communicated to persons in the facility, such as statusinformation, suggested actions, or instructions for taking actions. TheRSDs can include modular devices that enable various modular sensormodules to be installed therein, thereby enabling on-demand installationof sensors. The ISS may employ intelligence to monitor and learncharacteristics of the facility and/or persons, and adapt alerts and/orother operations to the learned characteristics.

FIG. 1 is a block diagram that illustrates an industrial facilityenvironment (“industrial facility”) in accordance with one or moreembodiments. In the illustrated embodiment, the industrial facility 100includes an industrial safety system (“ISS”) 102 and one or moreindustrial facility devices (“facility equipment”) 104. The ISS 102 caninclude a facility safety control system (“FSCS”) 106 and one or moreremote sensing devices (“RSDs”) 108. Various devices of the facility maybe communicatively coupled to one another by way of a network 107.

The network 107 can include an element or system that facilitatescommunication between the entities of the industrial facility 100. Forexample, the network 107 may include an electronic communicationsnetwork, such as a local area network (LAN), a wide area network (WAN),a wireless local area network (WLAN), a cellular communications network,a short range wireless communications network (e.g., a Bluetoothwireless network), the Internet, an industrial network, and/or the like.In some embodiments, the network 107 can include a single network or acombination of networks. As described, the RSDs 108 may communicatedirectly with the FSCS 106 via a distributed or distributed-meshnetwork, and/or may communicate directly with one another via a meshnetwork or a distributed-mesh network.

The industrial facility 100 can be, for example, an oil and gas plant, apower plant, and/or the like. The facility equipment 104 can includelarge machinery, electrical systems, flow control systems, and/or thelike of the industrial facility 100. Large machinery can include, forexample, turbomachinery, such as turbines, generators and compressorshaving components rotating at an extremely high rates. Electricalsystems can include, for example, power systems that generate andtransport high-voltage electrical power. Flow control systems caninclude, for example, flow control mechanisms, such as valves, pressurevessels and pipes that regulate the flow of substances, such as oil andnatural gas, at varying temperatures and pressures.

In some embodiments, the RSDs 108 include fixed-facility remote sensingdevices (or “fixed RSDs”) 108 a and/or mobile-personal remote sensingdevices (or “mobile RSDs”) 108 b that are distributed throughout theindustrial facility 100. A fixed RSD 108 a can include a RSD 108 thatremains stationary. A fixed RSD 108 a can include, for example, a RSD108 that is affixed to stationary facility equipment 104, such as aturbine, a generator, a compressor, a pump, a pressure vessel, and/or apipe, or otherwise provided in relatively stationary position, such asattached to a pole, scaffolding and/or another stationary structure ofthe facility 100. A mobile RSD 108 b can include a RSD 108 that isportable. A mobile RSD 108 b can include a personal RSD 108 that iscarried by or otherwise attached to a person 110 (e.g., a person workingin the facility 100) or mobile device 112 (e.g., a robot and/or drone)that can move throughout the facility 100. This can facilitate thepersonal RSDs 108 b moving throughout the facility 100 to provide formonitoring of conditions in areas of the facility 100 where persons 110are or are not located. In some embodiments, a mobile device 112includes a mobile wireless network hub (e.g., a “wireless networkhotspot”) that enables other network devices within the facility 100 toconnect to the network 107 by way of the mobile device 112. This can,for example, provide temporary network access in areas where thecommunication infrastructure within the facility 100 is disrupted (e.g.,during a safety incident), or can provide network access in areas wherea permanent network access point is not provided. In some embodiments, amobile device 112 can be certified and employed to inspect high riskareas, such as areas experiencing or susceptible to hazardous materialleaks, extremely high or low temperatures, and/or the like. For example,a certified mobile device 112 may be programmed to follow a route withinthe facility 100 to inspect high risk areas, regularly or in response toa safety event, such as detection of a gas leak to sense environmentalconditions in those areas.

In some embodiments, a RSD 108 includes a sensing unit 120, a processingunit 122, memory 124, a communications unit 126, and/or an alert unit128. The sensing unit 120 can include one more sensors for sensingvarious characteristics of the environment surrounding the RSD 108,including characteristics of a person 110 or a device (e.g., a piece offacility equipment 104 and/or a mobile device 112) the RSD 108 isattached to or is otherwise associated with. The sensors can include,for example, temperature sensors, flowrate sensors, pressure sensors,vibration sensors, gas detection sensors, microphones, health sensorsand/or location sensors. The alert unit 128 can include a device forpresenting alerts audibly, visually, and/or in a tactile manner. Forexample, the alert unit 128 may include a speaker for audiblybroadcasting alerts, a display screen or lights for visually displayingalerts, and/or a vibration mechanism for providing a tactile sensationto communicate an alert. The presentation of the alerts may be intendedfor receipt by the person 110 wearing the RSD 108 and/or other persons110 nearby the RSD 108. Corresponding alerts can also be provided, forexample, by way of external alert devices, such as displays or speakerslocated throughout the facility 100.

The processing unit 122 may provide for executing operational aspects ofthe RSD 108, such as receiving, sending and/or processing safetyinformation 136, and/or interacting with the facility equipment 104. Thesafety information 136 can include sensor data 138 indicative ofconditions sensed by sensors of the RSDs 108 and/or other sensingdevices, and/or safety alerts (“alerts”) 140 (e.g., includinginformation, instructions, control commands, and/or the like), such asthose described herein. In some embodiments, the memory 124 provides forstorage of data employed by the RSD 108, including program instructionsexecutable by the processing unit 122 to perform the operationsdescribed with regard to the RSD 108. In some embodiments, thecommunication unit 126 provides for the communication of data betweenthe RSD 108 and other devices of the facility 100, such as the FSCS 106and/or other RSDs 108, by way of the network 107. In some embodiments, aRSD 108 includes a computer device that is the same or similar tocomputer system 1000 described herein with regard to at least FIG. 8.

In some embodiments, the sensing unit of a mobile RSD 108 b includes oneor more sensors for sensing characteristics of the environmentsurrounding the mobile RSD 108 b, including characteristic of the person110 or mobile device 112 the mobile RSD 108 b is ultimately attached to.For example, the sensing unit 120 of a mobile RSD 108 b carried by aperson 110 working in the facility 100 may include a temperature sensorfor sensing the temperature of the environment surrounding the mobileRSD 108 b and the temperature of the person 110, a gas detection sensorfor sensing the presence and/or concentrations of gases in theenvironment surrounding the mobile RSD 108 b and the person 110, anacoustic sensor (e.g., a microphone) for sensing sounds in theenvironment surrounding the mobile RSD 108 b and the person 110, and/ora location sensor for sensing a geographic location of the mobile RSD108 b and the person 110, and/or health sensors for sensing healthcharacteristics of the person 110.

In some embodiments, the sensing unit of a fixed RSD 108 a includes oneor more sensors for sensing operational characteristics of the equipment104 the fixed RSD 108 a is ultimately attached to and/or characteristicsof the environment surrounding the equipment 104 the fixed RSD 108 a isultimately attached to. For example, the sensing unit of a fixed RSD 108a attached to pump may include pressure sensors for sensing the inputand output pressures of the pump, flowrate sensors for sensing the inputand output flowrates of the pump, temperature sensors for sensing theoperating temperature of the pump, the temperature of the fluid enteringand exiting the pump, and the temperature of the environment surroundingthe pump, vibration sensors for detecting vibrations of the pump, anacoustic sensors for sensing acoustic signatures of the pump and/orfluid flowing though the pump, gas detection sensors for sensing thepresence and/or concentrations of gases in the environment surroundingthe pump, and/or a location sensor for sensing a geographic location ofthe pump.

In some embodiments, the FSCS 106 includes a processing unit 130, memory132, and/or a communications unit 134. The processing unit 130 mayprovide for executing operational aspects of the FSCS 106, such asreceiving and/or sending safety information 136, processing the safetyinformation 136, and/or interacting with the facility equipment 104and/or RSDs 108 within the facility to monitor and/or controloperational aspects of the facility equipment 104 and/or the RSDs 108.In some embodiments, the FSCS 106 can communicate with external entitiesto acquire and disseminate relevant information. For example, the FSCS106 may receive current or forecast weather conditions from an externalweather provider, the FSCS 106 may receive reports of emergency responsepersonnel availability (e.g., firefighter and emergency medical services(EMS) availability) from an emergency response provider, and/orcommunicate needs for emergency response personnel to the emergencyresponse provider. In some embodiments, the FSCS 106 can adapt toconditions based on learned, historical patterns. For example, if aparticular set of conditions, such as a weather pattern, is determinedto preceded a given event, such as a gas leak, at least a predeterminednumber of times, the FSCS 106 may associate the set of conditions withthe event, and in response to identifying the occurrence, or theexpected occurrence of the set of conditions, the FSCS 106 maypreemptively issue a corresponding alert for the event, such asinstructing an inspection of an area of an anticipated gas leak inresponse to determining that a weather pattern associated with the gasleak is occurring or is forecast, based on the weather informationreceived from the external weather provider. The safety information 136can include sensor data 138 indicative of conditions sensed by sensorsof the RSDs 108 and/or other sensing devices, and/or alerts 140, such asthose described herein. In some embodiments, the memory 132 provides forstorage of data employed by the FSCS 106, including program instructionsexecutable by the processing unit 130 to perform the operationsdescribed with regard to the FSCS 106. In some embodiments, thecommunication unit 134 provides for the communication of data betweenthe FSCS 106 and other devices of the facility 100, such as the RSDs108, via the network 107. In some embodiments, the FSCS 106 includes acomputer device that is the same or similar to computer system 1000described herein with regard to at least FIG. 8.

The RSDs 108 of the facility 100 may operate in various configurations.With regard to communication, RSDs 108 may operate in a standalone (or“isolated”) configuration (e.g., the RSD 108 does not communicate withthe other RSDs 108 or the FSCS 106), a distributed (or “direct)configuration (e.g., the RSD 108 does not communicate with the other RSD108, but communicates directly with the FSCS 106), a meshedconfiguration (e.g., the RSDs 108 communicates with other RSD 108, butdoes not communicate directly with the FSCS 106), or a distributed-mesh(or “hybrid”) configuration (e.g., the RSD 108 communicates directlywith other RSD 108, and communicates directly with the FSCS 106). Withregard to processing, RSDs 108 may be configured for local processing(e.g., processing performed at the RSD 108, with the results not sharedwith the other RSDs 108), distributed processing (e.g., processingperformed by one or more RSD 108, with the results being shared betweenRSDs 108), centralized processing (e.g., processing performed at theFSCS 106), or hybrid processing (e.g., processing performed at one ormore RSDs 108 and/or the FSCS 106). With regard to management, RSDs 108may be self-managed (e.g., the RSD 108 controls operations performed bythe RSD 108) or centrally managed (e.g., operations of the RSD 108 arecontrolled by the FSCS 106).

In some embodiments, one or more RSDs 108 of the facility 100 operate ina standalone configuration, operating individually from one another.FIG. 2A is a diagram that illustrates RSDs 108 of the facility 100operating in a standalone (or “isolated”) configuration in accordancewith one or more embodiments. In a standalone configuration, there maybe no inter-communication between the RSDs 108 and/or the FSCS 106, asillustrated by the lack of arrows extending between the RSDs 108 and/orthe FSCS 106. In some embodiments, a RSD 108 operating in a standaloneconfiguration obtains sensor data 138 locally (e.g., the RSD 108 maycollect sensor data 138 from the sensors of the sensing unit 120 of theRSD 108), process the sensor data 138 locally (e.g., the RSD 108 mayprocess the sensor data 138 at the processing unit 122 of the RSD 108 todetermine whether an alert condition exits), and provides anycorresponding local alerts (e.g., the RSD 108 may present alerts 140indicative of an alert condition, locally by way of its alert unit 128).This may be done, for example, independent of communication with theother RSDs 108 and the FSCS 106 of the facility 100. Such independentoperation may provide relatively robust RSDs 108 that can operateindependent of an ability to establish communication with other devicesof the facility 100, including any of the other RSDs 108 and the FSCS106 of the facility 100. Moreover, such an embodiment can reduce theoverhead of data communications with other devices of the facility 100,including the other RSDs 108 and the FSCS 106 of the facility 100. Insome embodiments, a RSD 108 can communicate with external entities toacquire and disseminate relevant information. For example, a RSD 108 mayreceive information from an external entity, such as current andforecast weather conditions from an external weather provider and/orreports of emergency response personnel availability (e.g., firefighterand emergency medical services (EMS) availability) from an emergencyresponse provider, and forward the received information to otherentities in the facility 100, such as other RSDs 108 and/or the FSCS106, by way of the communications schemes described here.

In some embodiments, some or all of the RSDs 108 of the facility 100operate in a mesh configuration, sharing data with one another. FIG. 2Bis a diagram that illustrates RSDs 108 of the facility 100 operating ina mesh configuration in accordance with one or more embodiments. In amesh configuration, there may be intercommunication between the RSDs 108and no intercommunication between the RSDs 108 and the FSCS 106, asillustrated by the arrows extending between the RSDs 108 and the lack ofarrows extending between the RSDs 108 and the FSCS 106. In someembodiments, a RSD 108 operating in a mesh configuration obtains sensordata 138 locally and/or remotely (e.g., the RSD 108 may collect sensordata 138 from the sensors of the sensing unit 120 of the RSD 108 and/orreceive sensor data 138 collected and/or forwarded by another RSD 108),shares the obtained sensor data 138 with other RSDs 108 (e.g., the RSD108 may send the sensor data 138 it has collected and/or received toanother RSD 108), processes the sensor data 138 locally (e.g., the RSD108 may process the sensor data 138 it has collected and/or received atthe processing unit 122 of the RSD 108), shares the results of theprocessing, such as alerts 140, with other RSDs 108 (e.g., the RSD 108may send alerts 140 determined by the processing to another RSD 108and/or receive alerts 140 resulting from processing by another RSD 108,from the other RSD 108), and/or presents local alerts (e.g., the RSD 108may present alerts 140 determined by the RSD 108 and/or alerts receivedfrom other RSDs 108 locally, by way of it alert unit 128). This may bedone, for example, independent of communications by way of the FSCS 106.Such independent operations may provide robust RSDs 108 that can operateindependent of an ability to establish communication with the FSCS 106of the facility 100. Moreover, such an embodiment can reduce theoverhead of data communications with the FSCS 106 of the facility 100.

In some embodiments, some or all of the RSDs 108 of the facility 100operate in a distributed (or “direct) configuration, communicating byway of the FSCS 106. FIG. 2C is a diagram that illustrates RSDs 108 ofthe facility 100 operating in a distributed (or “direct”) configurationin accordance with one or more embodiments. In a distributedconfiguration, there may be intercommunication between the RSDs 108 andthe FSCS 106 and no intercommunication between the RSDs 108, asillustrated by the arrows extending between the RSDs 108 and the FSCS106 and the lack of arrows extending between the RSDs 108. In someembodiments, a RSD 108 operating in a distributed configuration obtainssensor data 138 locally (e.g., the RSD 108 may collect sensor data 138from the sensors of the sensing unit 120 of the RSD 108), forwards theacquired sensor data 138 to the FSCS 106 (e.g., the RSD 108 may send thesensor data 138 it has obtained to the FSCS 106), the FSCS 106 mayprocess the sensor data 138 locally (e.g., the FSCS 106 may process thesensors data 138 collected from one or more of the RSDs 108 locally atthe processing unit 130 to determine whether an alert condition exits,and any corresponding alerts 140), and/or the FSCS 106 may distributethe results of the processing, including any relevant correspondingalerts 140, to the RSDs 108 (e.g., the FSCS 106 may send a first alert140 for a first safety issue to a first RSD 108 determined to beassociated with the first safety issue and send a second alert for asecond safety issue to a second RSD 108 determined to be associated withthe second safety issue). The RSDs 108 may present any relevant alertsreceived (e.g., the first RSD 108 may present the first alert locally,by way of its alert unit 128, and the second RSD 108 may present thesecond alert locally, by way of its alert unit 128). This may be done,for example, with or without intercommunication between the RSDs 108themselves. In some embodiments, the FSCS 106 communicates safetyinformation 136 to RSDs 108 by way of unicast communication, multicastcommunication and/or broadcast communication. A unicast communicationmay include the FSCS 106 communicating information for receipt by aspecific-individual RSD 108 of available RSDs 108. A multicastcommunication may include the FSCS 106 communicating information forreceipt by a specific subset of two or more RSDs 108 of all availableRSDs 108. A broadcast communication may include the FSCS 106communicating information broadly for receipt by all available RSDs 108.Such centrally controlled processing may ensure a single, consistentinterpretation of the sensor data 138 and/or the execution of acoordinated set of alerts 140 across the RSDs 108. Moreover, such anembodiment can reduce the overhead of processing at the RSDs 108 byoff-loading processing to the FSCS 106, and reducing the “hops” that mayotherwise need to be performed to relay communications by way ofintermediate RSDs 108.

In some embodiments, some or all of the RSDs 108 of the facility 100operate in a distributed-mesh (or “hybrid”) configuration, communicatingwith one another directly in a manner similar to that described withregard to the mesh configuration and/or indirectly by way of the FSCS106 in a manner similar to that described with regard to the distributedconfiguration. FIG. 2D is a diagram that illustrates RSDs 108 of thefacility 100 operating in a distributed-mesh configuration in accordancewith one or more embodiments. In a distributed-mesh configuration, theremay be intercommunication between the RSDs and the FSCS 106 andintercommunication between the RSDs 108, as illustrated by the arrowsextending between the RSDs 108 and the FSCS 106 and the dotted arrowsextending between the RSDs 108. In some embodiments, a RSD 108 operatingin a distributed-mesh configuration obtains sensor data 138 locallyand/or remotely (e.g., the RSD 108 may collect sensor data 138 from thesensors of the sensing unit 120 of the RSD 108 and/or receive sensordata 138 collected and/or forwarded by another RSD 108), forwards theacquired sensor data 138 to the FSCS 106 (e.g., the RSD 108 may send thesensor data 138 it has obtained to the FSCS 106), the FSCS 106 mayprocess the sensor data 138 locally (e.g., the FSCS 106 may process thesensors data 138 collected from one or more of the RSDs 108 locally atthe processing unit 130 to determine whether an alert condition exits,and any corresponding alerts 140), and/or the FSCS 106 may distributethe results of the processing, including any relevant correspondingalerts 140, to the RSDs 108 (e.g., the FSCS 106 may send a first alert140 for a first safety issue to a first RSD 108 determined to beassociated with the first safety issue and send a second alert for asecond safety issue to a second RSD 108 determined to be associated withthe second safety issue). The FSCS 106 may identify RSDs 108 associatedwith particular issues based on a predefined association and/or learnedassociations. For example, if the FSCS 106 determines that a particularRSD 108 experiences a first safety issue at least a threshold number oftimes, the FSCS 106 may associate the RSD 108 with the first safetyissue, such that alerts 140 relating to the first safety issue are sentto the first RSD 108. In some embodiments, the RSD 108 also sharessafety information 136, such as acquired sensor data 138 and/or alerts140, with one or more other RSDs 108 (e.g., the RSD 108 may send thesensor data 138 it has collected and/or received, and/or alerts 140 ithas determined and/or received, to another RSD 108). The RSDs 108 maypresent any relevant alerts received (e.g., the first RSD 108 maypresent the first alert locally, by way of its alert unit 128, and thesecond RSD 108 may present the second alert locally, by way of its alertunit 128). As described herein, the sharing of safety information 136from one RSD 108 to one or more other RSDs 108 may be employed inresponse to the RSD 108 not being able to establish a reliable, directcommunication channel with the FSCS 106. In such an embodiment, one ormore intermediate RSDs 108 may act as intermediary nodes to relay thesafety information 136 from the RSD 108 to the FSCS 106. Such adistributed-mesh configuration may combine certain benefits ofdistributed configurations and mesh configurations. For example, adistributed-mesh configuration may, provide centrally controlledprocessing that can ensure a single, consistent interpretation of thesensor data 138 and/or the execution of a coordinated set of alerts 140across the RSDs 108, when possible. Moreover, such an embodiment canreduce the overhead of processing at the RSDs 108 by off-loadingprocessing to the FSCS 106, and reducing the “hops” that may otherwiseneed to be performed to relay communications by way of intermediate RSDs108, when possible. Further the distributed-mesh configuration may, whenneeded, enable independent operations to provide robust RSDs 108 thatcan operate independent of an ability to establish direct communication,or even indirect communication, with the FSCS 106 of the facility 100.

In some embodiments, such as in a mesh configuration or adistributed-mesh configuration, RSDs 108 provide safety information 136,such as collected safety data 138 and/or alerts 140, to other RSDs 108.For example, a RSD 108 may collect safety data 138 for various sensedcharacteristics of the environment surrounding the RSD 108 (e.g.,including characteristics of a person or device the RSD 108 is attachedto) the RSD 108 may process the collected safety data 138 locally todetermine whether an alert condition exists, and, in response todetermining that an alert condition exists, the RSD 108 may present acorresponding alert 140 locally and/or communicate safety information136, including the alert 140 and/or the safety data 138 collected, toother RSDs 108 that are in communication range (or “in range”) of theRSD 108 (e.g., in wireless communication range of the RSD 108 such thatthe RSD 108 can establish a wireless communication channel with theother RSDs 108 and transmit the safety information 136 to the other RSDs108 by way of the established wireless communication channel). The otherRSDs 108 receiving the safety information 136 may each, in-turn, presentthe alert 140 locally, process the safety data 138 locally, and/orcommunicate the safety information 136, including the alert 140 and/orthe safety data 138, to other RSDs 108 that are in range of that RSD108. Such an embodiment may enable the RSDs 108 of facility 100 toquickly disseminate critical safety information 136 (e.g., includingsafety data 138 and/or alerts 140) to nearby RSDs 108, thereby affordingpersons 110 and/or devices 112 wearing the mobile RSDs 108 (or in thevicinity of a fixed RSD 108) with an opportunity to immediately respondto the alerts 140. Such an embodiment may enhance robustness of the ISS102 by enabling the communication of safety information 136 (e.g.,including safety data 138 and/or alerts 140) even when traditionalcommunication paths, such as direct communication paths between the RSDs108 and the FSCS 106, are not available.

In some embodiments, such as in a distributed-mesh configuration, RSDs108 communicate safety information 136, such as collected safety data138 and/or alerts 140, with other RSDs 108 and/or the FSCS 106, based onavailable communication channels. For example, when communicating safetyinformation 136, a first RSD 108 may initially attempt to establishcommunication with the FSCS 106. If communication with the FSCS 106 canbe established, the first RSD 108 may then communicate the safetyinformation 136 to the FSCS 106. If, however, communication with theFSCS 106 cannot be established, the first RSD 108 may then attempt toestablish communication with another RSD 108. If communication with asecond RSD 108 is established then the first RSD 108 may communicate thesafety information 136 to the second RSD 108. A similar process can berepeated by the second RSD 108 and, if needed, by other RSDs 108, torelay the safety information 136 from the first RSD 108 to the FSCS 106by way of the one or more intermediate RSDs 108. Such an embodiment mayenhance robustness of the ISS 102 by enabling the communication ofsafety information 136 between RSDs 108 and the FSCS 106 by way ofintermediate RSDs 108 acting as intermediate communication nodes, evenwhen traditional communication paths, such as a direct communicationpath between the first RSD 108 and the FSCS 106, are not available.

In some embodiments, RSDs 108 communicate safety information 138 toanother RSD 108 based on characteristics of the other RSD 108, such as apower level of the other RSD 108 and/or proximity of the other RSD 108to the FSCS 106. For example, if a first RSD 108 determines that directcommunication with the FSCS 106 cannot be established, and that multipleother RSDs 108 are in range, it may query each of the other RSDs 108 inrange for proximity information indicating the proximity of the RSD 108to the FSCS 106 (e.g., a number of “hops” from the RSD 108 to the FSCS106, with 1 hop being a direct connection to the FSCS 106, 2 hops beinga connection to the FSCS 106 by way of a single intermediary RSD 108,and so forth) and/or for power information indicating a current powerlevel of the RSD 108 (e.g., the voltage level of a battery of the RSD108). In some embodiments, proximity of a RSD 108 may be determinedbased on a preconfigured assignment of the RSD 108, a geographiclocation of the RSD 108 (e.g., determined by way of a GPS location ofthe RSD 108), signal strength between the RSD 108 and the FSCS 106, by adynamic “hop query” and/or the like. For example, a RSD 108 may issue adynamic hop query to other RSDs 108 in range, requesting that theyreport the number of hops between themselves and the FSCS 106, and theRSD 108 may determine its own proximity by adding a “hop” to the lowestnumber of hops reported by the other RSDs 108 in range. In someembodiment, the FSCS 106 may periodically (e.g., every 1 minute, 5minute, 10 minute, 1 hour or the like) issue a central dynamic hop queryto each of RSDs 108 to determine the number of hops between the FSCS 106and each of the RSDs 108, the FSCS may 106 may store a hop table listingof the number of hops for each of the RSDs 108, and/or the FSCS 106 maybroadcast the hop table to the RSDs 108, and the RSDs 108 may use thehop-table to determine the proximity of itself and/or other RSDs 108 tothe FSCS 106. In some embodiments, the first RSD 108 may determinewhich, if any, of the other RSDs 108 in range have a power level above athreshold power level and are closest to the FSCS 106. If a single RSD108 is closest to the FSCS 106 and has a power level above the thresholdpower level (e.g., the RSD 108 is within 1 hop, and the other RSDs 108in range are within 2 hops or greater, or do not have a power levelabove the threshold power level), then the RSD 108 may communicate thesafety information 136 to the single RSD 108. If, however, multiple onesof the closest RSDs 108 have a power level above the threshold powerlevel and are the same proximity to the FSCS 106 (e.g., a second and athird RSD 108 both within 1 hop, and having a power level above thethreshold power level), the first RSD 108 may determine which of themultiple ones of the closest RSDs 108 having a power level above athreshold power level has the highest power level, and communicate thesafety information 136 to the RSD 108 having the highest power level. Ifthe RSD 108 determines that none of the other RSDs 108 in range have apower level above the threshold power level, the RSD 108 may send thesafety information 136 to the RSD 108 determined to have the highestpower level and/or broadcast the safety information 136 so that it canbe received by any of the RSDs 108 in range. A similar process can berepeated by the RSD 108 receiving the safety information from the firstRSD 108 and, if needed, by other RSDs 108, to relay the safetyinformation 136 from the first RSD 108 to the FSCS 106 by way of the oneor more intermediate RSDs 108 acting as intermediate communication nodesto complete the communication. Such an embodiment may help to optimizepower of RSDs 108 by avoiding relaying the safety information 136 usingRSDs 108 that already have a relatively low power supply which could befurther depleted by relaying the safety information 136 and, instead,employing RSDs 108 that have sufficient power to provide the relay ofthe safety information 136. Further, such an embodiment may employ arelatively short path to the FSCS 106 to reduce the number of relaysrequired to transmit the safety information 136 from the first RSD 108to the FSCS 106, saving both time and power associated withcommunicating the safety information 136 from the first RSD 108 to theFSCS 106.

FIG. 3A is a diagram that illustrates a method 300 of operating a RSD108 in a standalone configuration in accordance with one or moreembodiments. The method 300 may be executed, for example, by theprocessing unit 122 of the RSD 108. In some embodiments, the RSD 108monitors for safety data sensed (block 302). This can include, forexample, the RSD 108 monitoring safety data 138 sensed via the sensingunit 120 of the RSD 108. In response to sensing safety data (block 304),the RSD 108 may process the safety data (block 306). This can include,for example, the RSD 108 processing the safety data 138 locally todetermine whether an alert condition exists (block 308). In response todetermining that an alert condition exists, the RSD 108 may present analert (block 310). This can include the RSD 108 generating an alert 140corresponding to the alert condition and/or presenting the alert 140locally, via the alert unit 128 of the RSD 108. The alert 140 caninclude, for example, an audible and/or visual alert, such as thosedescribed herein (e.g., including lights, sirens and/or instructions).In some embodiments, in response to not sensing safety data (block 304),determining that an alert condition does not exists (block 308), orafter presenting an alert (block 310), the RSD 108 may return tomonitoring for safety data sensed (block 302).

FIG. 3B is a diagram that illustrates a method 320 of operating a RSD108 in a mesh configuration in accordance with one or more embodiments.The method 320 may be executed, for example, by the processing unit 122of the RSD 108. In some embodiments, the RSD 108 monitors for safetydata sensed and safety information from other RSDs (block 322). This caninclude, for example, the RSD 108 monitoring “local” safety data 138sensed via the sensing unit 120 of the RSD 108 and “remote” safetyinformation (e.g., safety data 138 and/or alerts 140) received fromother RSDs 108 in range. In response to sensing safety data (block 324)and/or receiving safety data from another RSD 108 (block 326), the RSD108 may send the safety data to in range RSDs 108 (block 328). This caninclude the RSD 108 broadcasting the obtained safety data 138, includingthe sensed “local” safety data 138 and/or the received “remote” safetydata 138, for receipt by other RSDs 108 that are in communication rangeof the RSD 108 (e.g., to relay the safety data 138 to other RSDs 108).In some embodiments, the RSD 108 may process the safety data (block330). This can include, for example, the RSD 108 processing the obtainedsafety data 138, including the sensed local safety data 138 and/or thereceived remote safety data 138, locally to determine whether an alertcondition exists (block 332). In response to determining that an alertcondition exists, the RSD 108 may present an alert (block 334). This caninclude the RSD 108 generating an alert 140 corresponding to the alertcondition determined and/or presenting the alert 140 locally, via thealert unit 128. The alert 140 can include, for example, an audibleand/or visual alert, such as those described herein (e.g., includinglights, sirens and/or instructions). In some embodiments, the RSD 108may send the alert to in range RSDs 108 (block 336). This can includethe RSD 108 broadcasting the alert 140 for receipt by other RSDs 108that are in communication range of the RSD 108 (e.g., to relay the alert140 to other RSDs 108). In some embodiments, in response to receiving analert (block 338), the RSD 108 may proceed to present the alert (block334) and/or send the alert to in range RSDs 108 (block 336). This caninclude the RSD 108 receiving an alert 140 broadcast from an in rangeRSD 108, and proceeding to present the alert 140 (e.g., if it isdetermined to be relevant to the RSD 108) and/or proceeding to broadcastthe alert 140 for receipt by other RSDs 108 that are in communicationrange of the RSD 108 (e.g., to relay the alert 140 to the other RSDs108). In some embodiments, in response to receiving an alert 140 (block338), the RSD 108 may proceed to processing the alert 140 as safety data(block 330) to further assess the content of the alert 140, and make itsown assessment of whether the alert 140 rises to the level of an alertcondition (block 332). In some embodiments, in response to not sensingsafety data (block 324), not receiving safety data (block 326),determining that an alert condition does not exists (block 332), orafter presenting an alert (block 334) and/or sending the alert 140 to inrange RSDs 108, the RSD 108 may return to monitoring for safety datasensed (block 322).

FIG. 3C is a diagram that illustrates a method 350 of operating a RSD108 in a distributed configuration in accordance with one or moreembodiments. The method 350 may be executed, for example, by theprocessing unit 122 of the RSD 108. In some embodiments, the RSD 108monitors for safety data sensed and safety information received from theFSCS 106 (block 352). This can include, for example, the RSD 108monitoring “local” safety data 138 sensed via the sensing unit 120 ofthe RSD 108 and “remote” safety information 136 (e.g., safety data 138and/or alerts 140) received from the FSCS 106. Receipt of the safetyinformation 136 may include receipt of a “wakeup” signal to activate theRSD 108. In response to sensing safety data (block 354), the RSD 108 maydetermine whether communication with the FSCS 106 is available (block356). Such a conditional response may reduce power consumption, as theRSD 108 may operate in a relatively low-power state until receipt of thesafety information 136 (e.g., including a wakeup signal), and may thentransition into a relatively high-power active state in which itassesses the state of communication with the FSCS 106. In response todetermining that communication with the FSCS 106 is not available, theRSD 108 may queue the sensed safety data 138 (e.g., store the safetydata 138 in a memory 124 of the RSD 108) and send the queued safety data138 to the FSCS 106 when communication with the FSCS 106 is available(block 358). In some embodiments, in response to determining thatcommunication with the FSCS 106 is not available, the RSD 108 mayreconfigure itself into another mode of operation to enablecommunication of the safety data 138, such as a meshed configuration. Inresponse to determining that communication with the FSCS 106 isavailable, the RSD 108 may send the safety data 138 to the FSCS 106(block 360). This can include the RSD 108 sending the safety date 138directly to the FSCS 106 by way of a direct communication channelestablished there between. In some embodiments, the RSD 108 may processthe safety data (block 362). This can include, for example, the RSD 108processing the sensed safety data 138 locally to determine whether analert condition exists (block 364). In response to determining that analert condition exists, the RSD 108 may present an alert (block 366).This can include the RSD 108 generating an alert 140 corresponding tothe alert condition and/or presenting the alert 140 locally, via thealert unit 128. The alert 140 can include, for example, an audibleand/or visual alert, such as those described herein (e.g., includinglights, sirens and/or instructions). In some embodiments, the RSD 108may send the alert to the FSCS 106 (block 368). In some embodiments, inresponse to receiving an alert (block 370), the RSD 108 may proceed topresent the alert (block 366). This can include the RSD 108 receiving analert 140 from the FSCS 106, and proceeding to present the alert 140locally, via the alert unit 128. In such an embodiment, the RSD 108 maynot send the received alert 140 back to the FSCS 106. In someembodiments, in response to receiving an alert 140 (block 370), the RSD108 may proceed to processing the alert 140 as safety data (block 362)to further assess the content of the alert 140, and make its ownassessment of whether the alert 140 rises to the level of an alertcondition (block 364). In some embodiments, in response to not sensingsafety data (block 354), not receiving an alert (block 370), determiningthat an alert condition does not exists (block 364), or after presentingan alert (block 366) and/or sending the alert 140 to the FSCS 106, theRSD 108 may return to monitoring for safety data sensed (block 352).

FIG. 3D is a diagram that illustrates a method 380 of operating a RSD108 in a distributed-mesh configuration in accordance with one or moreembodiments. The method 380 may be executed, for example, by theprocessing unit 122 of the RSD 108. In some embodiments, the RSD 108 maymonitor for safety data sensed and safety information from other RSDsand/or the FSCS 106 (block 382). This can include, for example, the RSD108 monitoring “local” safety data 138 sensed via the sensing unit 120of the RSD 108 and “remote” safety information (e.g., safety data 138and/or alerts 140) received from other RSDs 108 in range and/or the FSCS106. In response to sensing safety data (block 384) and/or receivingsafety data from another RSD 108 (block 385), the RSD 108 may determinewhether communication with the FSCS 106 is available (block 386). Inresponse to determining that communication with the FSCS 106 is notavailable, the RSD 108 may send the obtained safety data to in rangeRSDs 108 (block 388). This can include the RSD 108 broadcasting thesensed and/or received safety data 138, including the sensed “local”safety data 138 and/or the received “remote” safety data 138, forreceipt by other RSDs 108 that are in communication range of the RSD 108(e.g., to relay the safety data 138 to other RSDs 108). In response todetermining that communication with the FSCS 106 is available, the RSD108 may send the safety data 138 to the FSCS 106 (block 390). In someembodiments, the RSD 108 may process the safety data (block 392). Thiscan include, for example, the RSD 108 processing the sensed safety data138 locally to determine whether an alert condition exists (block 394).In response to determining that an alert condition exists, the RSD 108may present an alert (block 396). This can include the RSD 108generating an alert 140 corresponding to the alert condition and/orpresenting the alert 140 locally, via the alert unit 128. The alert 140can include, for example, an audible and/or visual alert, such as thosedescribed herein (e.g., including lights, sirens and/or instructions).In some embodiments, the RSD 108 may send the alert to the FSCS 106(block 397) and/or to in range RSDs 108 (block 398). In someembodiments, in response to receiving an alert (block 399), the RSD 108may proceed to present the alert (block 396). This can include the RSD108 receiving an alert 140 from the FSCS 106 and/or another RSD 108, andproceeding to present the alert 140 locally, via the alert unit 128. Insuch an embodiment, the RSD 108 may not send an alert 140 received fromthe FSCS 106 back to the FSCS 106 and may not send an alert 140 receivedfrom a RSD 108 back to the RSD 108 in an effort to reduce networktraffic. In some embodiments, in response to receiving an alert 140(block 399), the RSD 108 may proceed to processing the alert 140 assafety data (block 392) to further assess the content of the alert 140,and make its own assessment of whether the alert 140 rises to the levelof an alert condition (block 394). In some embodiments, in response tonot sensing safety data (block 384), not receiving safety data (block385), not receiving an alert (block 399), determining that an alertcondition does not exists (block 394), or after presenting an alert(block 396) and/or sending the alert 140 to the FSCS 106 (block 397)and/or to in range RSDs 108 (block 398), the RSD 108 may return tomonitoring for safety data sensed and safety information (block 382).

In some embodiments, presentation (or “execution”) of an alert 140includes an audible and/or visual representation of the alert. Forexample, presentation of an alert 140 by a RSD 108 can include the RSD108 providing a siren and/or a flashing light. Such presentation of analert 140 may alert nearby persons 110 to the alert condition and/or canfacilitate locating a person 110, device 112 or equipment 104 associatedwith the RSD 108 that is the subject of the alert 140. For example, inthe case of a fire, a RSD 108 worn by a person 110 that emits a sirenand flashing light can enable a firefighter or other response personnelto locate the person 110. In some embodiments, an alert 140 presented bya RSD 108 includes a “local” alert 140 generated by the RSD 108 based onprocessing of local data 138 and/or remote safety information 136, or a“remote” alert 140 received by the RSD 108 from an in range RSD 108(e.g., relayed to the RSD 108 from another RSD 108 or the FSCS 106) orfrom the FSCS 106 (e.g., via direct communication with the FSCS 106).

In some embodiments, the contents of an alert 140 includes suggestedactions or instructions for taking actions to respond to thecorresponding alert condition. For example, presentation of an alert 140by a RSD 108 can include the RSD 108 providing instructions foroperating nearby equipment to resolve the source of the alert 140 (e.g.,“Close valve 1 to stop the ongoing gas leak”). As a further example,presentation of an alert 140 by a RSD 108 can include the RSD 108providing instructions for evacuating an area or otherwise navigatingaway from a dangerous condition. This can include, for example,directions for navigating around a potentially hazardous area (e.g.,“Move immediately to Area 1 by way of Area 2 and Area 4; Avoid Areas 3and 5”). In some embodiments, such an alert 140 is presented visuallyand/or audibly. For example, the RSD 108 may provide display of a map ofthe facility 100 and/or a route for navigating around the potentiallyhazardous area, such as a map depicting areas 1-7, an icon indicatingthe current position of the RSD 108, highlighting Areas 3 and 5 in red,highlighting Area 1 in green, and highlighting a route through Areas 2and 4 in blue. As a further example, the RSD 108 may also provideaudible instructions for navigating around potentially hazardous area,such as broadcasting via a speaker, the instructions “Move immediatelyto Area 1 by way of Area 2 and Area 4 . . . . Avoid Areas 3 and 5”. Insome embodiments, alerts 140 can be provided throughout the facility100. For example, a first color of lights may be activated in thepotentially hazardous area (e.g., red flashing lights illuminated inAreas 3 and 5), a second color of lights may be activated along a routeto safe zone (e.g., blue flashing lights in Areas 2 and 4), and a thirdcolor of lights may be activated in the safe zone (e.g., green flashinglights in Area 1). In some embodiments, lights may be illuminatedsequentially to illustrate a path for persons to follow to the safezone. For example, a blue flashing lights may be illuminated in sequenceone after the other along the route through Areas 2 and 4, to guidepersons to Area 1 by following the sequential illumination of thelights. In some embodiments, presentation of an alert 140 can includeinstructions for assisting one or more persons. For example, if a firstRSD 108 worn by a person 110 senses that the person 110 has fallen, isexposed to a gas and is not moving, or is otherwise experiencing apotentially hazardous situation, an alert 140 can be provided to one ormore other nearby mobiles RSD 108 determined to be within range of theRSD 108, and presentation of the alert 140 can include directions fornavigating to the person 110 (e.g., in a similar manner as providing aroute to a safe zone) and/or instructions for assisting the person 110.In some embodiments, it can be determined for each of one or more RSDs108, whether suggested actions of an alert 140 sent to the RSD 108 wouldexpose a person associated with the RSD 108 to a risk at or above athreshold level, and the alert 140 may be provided to RSDs 108 for whichit is determined that the suggested action of the alert 140 would notexpose the persons associated with the RSDs 108 to a risk at or abovethe threshold level, and the alert 140 may not be provided to RSDs 108for which it is determined that the suggested action of the alert 140would expose the persons associated with the RSDs 108 to a risk at orabove the threshold level. The instructions can include instructions ofhow to evaluate the status of the person 110 (e.g., “Ask the person ifthey are having trouble breathing”), instructions to treat any medicalissues experienced by the person 110 (e.g., “If the person is havingtrouble breathing, administer oxygen via a portable oxygen unit and waitfor medical responders to arrive”), and/or instructions to move theperson 110 out of the area (e.g., “If the person is breathingcomfortably, move them to Area 1 for further treatment”).

In some embodiments, alerts 140 issued to a RSD 108 may be based on thelocation of the RSD 108. For example, an alert 140 may include differentinstructions for RSDs 108 in different locations. In the case of analert 140 including directions for navigating around a potentiallyhazardous area, alerts 140 provided to RSDs 108 may provide safe andefficient routes for evacuating from the respective positions of theRSDs 108. For example, alerts 140 issued to one or more RSDs 108determined to be in Area 2 may include instructions to follow a firstpath for evacuating the area (e.g., “Move immediately to Area 1 by wayof Area 4”), and alerts 140 issued to one or more RSDs 108 determined tobe in Area 6 may include instructions to follow a second path forevacuating the area (e.g., “Move immediately to Area 9 by way of Area 7and Area 8”).

In some embodiments, the contents of an alert 140 is based oncharacteristics of the safety issue that is the source of the alert 140.For example, in the case of receiving safety information 136 indicatinga hazardous gas being detected, and determining that the hazardous gasis relatively heavy (and thus concentrates in relatively low locations,such as those near the ground), the presentation of the correspondingalert 140 may include an indication of the type of gas leak and provideinstructions for persons to remain standing and keep their headselevated to avoid inhaling the gas.

In some embodiments, the contents of an alert 140 is based oncharacteristics of the safety issue that is the source of the alert 140,and determinations as to how the safety issue will evolve. For example,in the case of receiving safety information 136 indicating a hazardousgas being detected at a first location (e.g., hazardous gas beingdetected in Area 3), wind speed and direction data for the location(e.g., a Northwest wind of 3 miles per hour) can be used to determine orpredict that the gas has or will spread into a downwind location (e.g.,to predict that the gas has or will spread into Area 5 which is locatedSoutheast of Area 3). As a result, alerts 140 can be communicated toRSDs 108 determined to be located at or near the affected locations(e.g., alerts can be communicated to RSDs 108 determined to be locatedin affected Areas 3 and 5). Such an embodiment can enable the system 106to proactively present alerts 140 to persons 110 located in areas thatare determined or predicted to be affected, but at which a local safetyissue not yet been sensed or determined.

In some embodiments, a RSD 108 generates alerts 140 based on locallysensed safety data 138 and/or safety data 138 obtained by way of otherRSDs 108. For example, in an instance in which a first RSD 108 does notestablish communication with a central controller (e.g., the RSD 108 isoperating a local processing mode, or reliable communication with theFSCS 106 cannot be established), the first RSD 108 may obtain safetyinformation 136 from other RSDs 108 in range (e.g., including safetydata 138 acquired by and/or alerts 140 generated by the other RSDs 108)and process the safety information 136 locally to determine what, ifany, alert 140 should be generated by the first RSD 108. As an example,upon the first RSD 108 determining that a gas leak has occurred at ornear the first RSD 108 (e.g., by way of the first RSD 108 sensing theconcentration of the gas at the first RSD 108 and/or the first RSD 108receiving safety information 136 from another RSD 108 indicating the gasleak), the first RSD 108 may, then, query the other RSDs 108 in rangefor safety information 136 (e.g., including safety data 138 including anindication of the concentration of gases sensed by the other RSDs 108and the location of the other RSDs 108), and upon the first RSD 108receiving the safety information 136, the first RSD 108 may process thesafety information 136 received to determine the locations andconcentrations of the gas (e.g., process the safety information 136received to determine the locations and concentrations of the gas todetermine that Areas 3 and 5 have relatively high concentrations of thegas and that Areas 2 and 4 have relatively low or no concentrations ofthe gas), the first RSD 108 may determine a route for moving to a safezone that includes passing through locations with the least gasconcentrations (e.g., a route to a safe zone in Area 1 by way of Area 2and Area 4), and the first RSD 108 may issue a corresponding local alert140 (e.g., the first RSD 108 may display or audibly recite directions to“Move immediately to Area 1 by way of Area 2 and Area 4 . . . . AvoidAreas 3 and 5” along with a graphical depiction of the route, asdescribed herein). In some embodiments, a RSD 108 or the FSCS 106 cancommunicate directly with devices 104 of the facility 100 to controloperation of the devices 104. For example, in the event the RSD 108determines that a leak is occurring in a first region controlled by afirst valve, the RSD 108 may send an instruction to the first valve toclose, to eliminate the leak.

In some embodiments, a RSD 108 can be operated in different sensingmodes based on current conditions. For example, a RSD 108 may beoperated in a first mode (e.g., a low-power, low sensitivity sensingmode) under normal operating conditions and, in response to determiningthat an alert condition exists (e.g., sensing abnormal conditions orreceiving an alert 140), the RSD 108 may be operated in a second mode(e.g., a high-power, high sensitivity sensing mode). Such an embodimentmay enable the RSD 108 to save power (e.g., by reducing powerconsumption during normal operations), and still provide sufficientlevels of sensing when an alert condition exists (e.g., by switching toa more sensitive sensing mode when an alert condition exists).

In some embodiments, a RSD 108 is modular, including a modular sensingunit 120 that enables one more sensors to be installed into and/orremoved from the sensing unit 120 of the RSD 108. FIG. 4 is a diagramthat illustrates a RSD 108 employing a modular sensing unit 120 inaccordance with one or more embodiments. In some embodiments, themodular sensing unit 120 includes a sensor bay 400 having sensor moduleslots 402 for receiving sensor modules 404. For example, first, second,third, fourth and fifth sensor modules 404 can be installed into thefirst, second, third, fourth and fifth sensor module slots 402,respectively. In some embodiments, each of the sensor module slots 402has a given profile and each of the sensor module 404 has acomplementary profile, such that each of the sensor modules 404 can beinstalled into in any of the sensor module slots 402. This may allow aperson 110 to easily exchange sensor modules 404 on demand, as theirneeds dictate. A sensor module 404 can include, for example, atemperature sensor module including one or more temperature sensors, aflowrate sensor module including one or more flowrate sensors, apressure sensor module including one or more pressure sensors, avibration sensor module including one or more vibration sensors, a gasdetection sensor module including one or more gas detection sensors, anacoustic sensor module including one or more acoustic sensors, and/or alocation sensor module including one or more location sensors. In someembodiments, a sensor module 404 can include a power source (e.g., arechargeable battery pack) that can provide electrical power foroperating the RSD 108 when installed into a sensor module slot 402 ofthe RSD 108. Various combinations of sensor modules 404 can be installedto provide different combinations of sensors in the RSD 108. Forexample, a temperature sensor module 404 and a location sensor module404 may be installed into the sensor bay 400 to enable the RSD 108 tosense temperature and location. A gas detection sensor module 404 may besubsequently installed to enable the RSD 108 to sense temperature,location and the presence/concentration of certain gases. Thetemperature sensor module 404 may be exchanged with a vibration sensormodule 404, to enable the RSD 108 to sense vibrations, location and thepresence/concentration of certain gases. In some embodiments, a sensormodule 404 can be installed into or removed from a sensor module slot402 by simply sliding the sensor module 404 into or out of the sensormodule slot 402, as illustrated by the arrow. A sensor module slot 402and/or a sensor module 404 may include a latching mechanism to securethe sensor module 404 in the sensor module slot 402. A sensor module 404may include an electrical connection that mates with a complementaryelectrical connection of a sensor module slot 402 to enablecommunication between the sensor module 404 and the processing unit 130of the RSD 108 and/or for transmitting electrical power between a powersource of the RSD 108 and the sensor module 404. Such modularembodiments may improve the flexibility of the sensing unit 120, the RSD108 and the ISS 102 as a whole. For example, a sensor module 404 can beinstalled into and/or removed from a RSD 108 on-demand, to meet currentneeds. In some embodiments, a sensor module 404 can be controlledremotely. For example, a sensor module 404 may be remotely enabled ordisabled by the FSCS 106. In some embodiments, the RSD 108 may need tobe a physically “safe” module to satisfy safety requirements inhazardous parts of the plants. For example, the RSD 108 may need to meetrequirements to inhibit the ignition of hazardous materials, such asflammable gases and liquids. To meet such requirements, in someembodiments, an interface between the sensor module 404 and the RSD 108can include a wireless connection, such as a near field communication(NFC) or Bluetooth connection). In some embodiments, such as wherewireless connections between the sensor module 404 and the RSD 108 areemployed, there are no exposed physical wires or pins between the sensormodule 404 and the RSD 108, eliminating potential ignition sources. Insome embodiments, the modules 404 or the RSD 108 include local powersources, such as low voltage batteries. In some embodiments, the modules404 or the RSD 108 each includes an energy harvesting device that iscapable of charging batteries of the respective device, such as a devicefor harvesting energy from movement of the respective device.

A person 110 may be alerted to install certain types of sensor modules404 based on a location associated with the person 110 and/or the RSD108 associated with the person 110. In some embodiments, a person 110 isalerted to install one or more sensor modules 404 into their RSD 108based on one or more locations the person 110 is scheduled to work in.For example, if the FSCS 106 determines that a person 110 is scheduledto work a shift in a first region of the facility 100 categorized asbeing prone to high temperatures, then the FSCS 106 may, at thebeginning of the shift, send to the RSD 108 associated with that person110, an alert 140 advising the person 110 to install a temperaturesensor module 404 in the RSD 108 for the duration of the shift. The RSD108 may present the alert 140 for receipt by the person 110, and maycontinue to present the alert 140 until the RSD 108 detects that atemperature sensor module 404 is installed into a sensor module slot 402of the sensor bay 400 of the sensing unit 120 of the RSD 108. In such anembodiment, the person 110 may simply install a temperature sensormodule 404 into a sensor module slot 402 of the RSD 108 to satisfy thealert 140. The person 110 may simply remove the a temperature sensormodule 404 from the sensor module slot 402 at the completion of theshift, after exiting the first region.

In some embodiments, a person 110 is alerted to install one or moresensor modules 404 into their RSD 108 based on a current location of theperson 110 and/or the RSD 108. For example, if the FSCS 106 determinesthat a RSD 108 worn by (or otherwise associated with) a person 110 islocated in a second region of the facility 100 categorized as beingprone to gas leaks, then the FSCS 106 may send to the RSD 108, an alert140 advising the person 110 to install a gas detection sensor module 404in the RSD 108 while they are located in the second region. The RSD 108may present the alert 140 for receipt by the person 110, and maycontinue to present the alert 140 until the RSD 108 detects that the gasdetection module 404 is installed into a sensor module slot 402 of theRSD 108. In such an embodiment, the person 110 may simply install a gasdetection sensor module 404 into a sensor module slot 402 of the RSD 108to satisfy the alert 140. The person 110 may simply remove the gasdetection sensor module 404 from the sensor module slot 402 afterexiting the second region.

FIG. 5 is a block diagram that illustrates a method 500 for operating anISS 102 employing modular RSDs 108 in accordance with one or moreembodiments. Method 500 can include determining one or more locationsassociated with a RSD (block 502), determining one or more sensormodules associated with the one or more locations (block 504), andgenerating an alert to install the one or more sensor modules in the RSD(block 506). In some embodiments, the operations of method 500 areperformed by the RSD 108 and/or the FSCS 106.

In some embodiments, determining one or more locations associated with aRSD (block 502) includes determining one or more locations associatedwith a RSD 108 associated with a person 110. Determining one or morelocations associated with a RSD 108 associated with a person 110 mayinclude the FSCS 106 determining that a RSD 108 is associated with oneor more regions of a facility 100 based on a person 110 the RSD 108 isassigned to, or otherwise associated with, being scheduled to work ashift in the one or more regions of the facility 100. In such anembodiment, before or during the shift, the FSCS 106 may access a workschedule for the person 110 and/or other persons 110 working in thefacility (e.g., a work schedule stored in memory 132) that specifies oneor more regions of the facility 100 (e.g., Areas 4 and 5) the person 110is scheduled to work in during the shift, and identify those regions(e.g., Areas 4 and 5) as locations associated with the RSD 108. Asanother example, determining one or more locations associated with a RSD108 associated with a person 110 can include the FSCS 106 and/or a RSD108 determining one or more regions in which the RSD 108 is located in.In such an embodiment, the FSCS 106 and/or a RSD 108 may determine acurrent physical location of the RSD 108, determine one or more regionsof the facility 100 that include the location (e.g., Area 3), andidentify the one or more regions as the location associated with the RSD108. The RSD 108 and/or the FSCS 106 may determine a physical locationof the RSD 108, for example, based on a location sensed by a locationsensor (e.g., global positioning system (GPS) sensor) of the RSD 108.The FSCS 106 may determine the physical location based on a physicallocation of the RSD 108 indicated in safety data 138 communicated fromthe RSD 108 to the FSCS 106.

In some embodiments, determining one or more sensor modules associatedwith the one or more locations (block 504) includes determining one ormore sensor modules 404 that are suggested or required to be employed atthe one or more locations. Referring to the first example, determiningone or more sensor modules 404 that are suggested or required to beemployed at the one or more locations may include the FSCS 106 and/orthe RSD 108 determining that a temperature sensor module is to beemployed in the identified regions of the facility 100 that the person110 is scheduled to work in during their shift (e.g., a temperaturesensor module is required in Areas 4 and 5 that the person 110 isscheduled to work in during their shift). Referring to the secondexample, determining one or more sensor modules 404 that are suggestedor required to be employed at the one or more locations may include theFSCS 106 and/or the RSD 108 determining that a gas detection sensormodule is to be employed in the region of the facility 100 including thelocation (e.g., a gas detection sensor module is required in Area 3 inwhich the RSD 108 is determined to be located).

In some embodiments, generating an alert to install the one or moresensor modules in the RSD (block 506) includes generating and/orpresenting an alert 140 to advise a person 110 to install the one ormore sensor modules 404 in the RSD 108. Referring to the first example,generating an alert 140 to advise a person 110 to install the one ormore sensor modules 404 in the RSD 108 may include the FSCS 106generating and sending to the RSD 108, and/or the RSD 108 generatingand/or presenting, an alert 140 to advise the person 110 to install atemperature sensor module 404 in the RSD 108. Presentation of the alert140 may include, for example, the RSD 108 displaying and/or audiblyreciting the message “You are required to install a temperature sensormodule for visiting Areas 4 and 5 during your shift today” and/orilluminating a yellow flashing light and/or sounding a buzzer toindicate that a required temperature sensor module 404 is not installedin the RSD 108. The RSD 108 may continue to present the alert 140 untilthe RSD 108 detects that a temperature sensor module 404 is installed inthe RSD 108, or the person has exited Areas 4 and 5 and the shift hasended. Referring to the second example, generating an alert 140 toadvise a person 110 to install the one or more sensor modules 404 in theRSD 108 may include the FSCS 106 generating and sending to the RSD 108,and/or the RSD 108 generating and/or presenting, an alert 140 to advisethe person 110 to install a gas detection sensor module 404 in the RSD108. Presentation of the alert 140 may include, for example, the RSD 108displaying and/or audibly reciting the message “You are required toinstall a gas detection sensor module while located in Area 3” and/orilluminating a yellow flashing light and/or sounding a buzzer toindicate that a required sensor module 404 (e.g., a gas detection sensormodule 404) is not installed in the RSD 108. The RSD 108 may continue topresent the alert 140 until the RSD 108 detects that a gas detectionsensor module 404 has been installed in the RSD 108, or the RSD 108 hasmoved out of the region (e.g., the RSD 108 has moved out of out of Area3). The external presentation of an alert 140, such as a flashing lightand/or buzzer, may help to alert the person 110 and other persons 110near the RSD 108 that a required sensor module 404 is not installed inthe RSD 108. In such an embodiment, the other persons 110 may becomeaware of the situation, alert the person 110 to the situation, and/orotherwise remind and encourage the person 110 to install the requiredsensor module 404 and/or leave the region.

In some embodiments, the facility 100 may include one or more stationsfor providing sensor modules 404. For example, the industrial facility100 may include kiosk located throughout the facility that have multiplesensor modules 404 of varying types that can be taken by persons 110 forinstallation into their RSD 108 (e.g., prior to entering a region of thefacility 100 requiring the sensor module 404) and/or can be uninstalledfrom the RSD 108 and returned to a kiosk in the facility 100 once theyare no longer needed by the person 110 (e.g., after leaving a region ofthe facility 100 requiring the sensor module 404). In some embodiments,the kiosk can include automated vending machines that automaticallydistribute a sensor module 404 suggested and/or required to be used by aperson 110 and/or the RSD 108 associated with the person. For example, aperson 110 may approach a kiosk, enter information indicating whichregions they will be working in (e.g., the person 110 selects areas 4and 5 from a map displayed on the kiosk), the kiosk may provide anindication of the suggested and/or required sensor modules 404 for theregions (e.g., displaying and/or audibly reciting the message “You arerequired to install a temperature sensor module for visiting Areas 4 and5 during your shift today . . . ”), provide an option to select whichsensor modules 404 the person 110 does and/or does not already haveinstalled in their RSD 108 (“ . . . please select the sensor modules youalready have installed in your RSD”), and may automatically dispense thesensor modules 404 the person 110 does not already have installed intheir RSD 108 for installation in the RSD 108. In some embodiments,enter information indicating which regions the person 110 will beworking in can include the person 110 submitting a personal identifier(e.g., an employee identifier), and the kiosk may determine the areasthe person 110 will be working in based on a work schedule for theperson 110, as described herein, such that the kiosk will automaticallyrecommend and/or dispense the sensor modules 404 suggested and/orrequired for the shift of the person 110. In some embodiments, a kioskmay be located at the entrance to or in a region, and may automaticallyrecommend and/or dispense the sensor modules 404 suggested and/orrequired for working in the region. In some embodiments, a sensor module404 physically installed in a RSD 108 may be activated (e.g., enabledfor use) or deactivated (e.g., disabled for use). For example,installation of a sensor module 404 into a RSD 108 may includephysically installing the module 404 into the RSD 108 and/or activatingthe sensor module 404. Un-installing a sensor module 404 from a RSD 108may include physically removing the module 404 from the RSD 108 and/orde-activating the sensor module 404.

Such embodiments of modular sensing units 120 may enable RSDs 108 to becustomized to meet particular monitoring needs. This can help to reducethe physical weight and size of the RSDs 108, for example, byeliminating the need to carry unneeded sensors, and can improveperformance, for example, by reducing power consumption that mayotherwise be attributable to unneeded sensors drawing power to operate.Moreover, the ability to add and remove sensor modules 404 can reducethe overall number of sensors used by a facility 100, as each person 110can add and remove sensor on-demand to meet their individual needs, anddoes not need to continually carry the full array of sensors for theentire facility 100. Further, such embodiments can help to ensure thatpersons 110 in a facility 100 are carrying appropriate sensors whileworking in and moving about the facility 100.

In some embodiments, the ISS 102 employs intelligence to monitor andlearn characteristics of the facility 100 and/or persons 110, and adaptsalerts 140 and/or other operations to the learned characteristics. Insome embodiments, the FSCS 106 dynamically categorizes conditions basedon responses to corresponding alerts 140. For example, the FSCS 106 maycategorize each of a plurality of sets of conditions in different riskcategories. This can include, for example, categorizing a first set ofconditions (e.g., a relatively high temperature detected by a single RSD108) in a low risk category, categorizing a second set of conditions(e.g., a relatively high temperature detected by two or more RSD 108 inthe same region of the facility 100) in a moderate risk category, andcategorizing a third set of conditions (e.g., a relatively hightemperature detected by RSD 108 in adjacent regions of the facility 100)in a high risk category. Each of the risk categories may be associatedwith a corresponding type of alert 140. For example, the low riskcategory may be associated with a relatively low priority local alert140 (e.g., sending an alert 140 to only the RSD 108 that detected therelatively high temperature), the moderate risk category may beassociated with a relatively moderate priority regional alert 140 (e.g.,sending an alert 140 to all of the RSDs 108 currently located in theregion in which the two or more RSD 108 detected the relatively hightemperature and/or sounding an alarm and/or flashing warning lights inthe region), and the high risk category may be associated with arelatively high priority, plant-wide alert 140 (e.g., sending an alert140 to all of the RSDs 108 located in the facility 100 and/or soundingan alarm and/or flashing warning lights across the entire facility 100).

During operations, the FSCS 106 may collect safety data 128 from one ormore RSD 108 and/or one or more other sensing device located throughoutthe facility 100, and process the safety data 128 to determine currentconditions in the facility 100. In response to determining that aparticular set of conditions associated with a risk is encountered, theFSCS 106 may issue a corresponding alert 140. For example, in responseto the FSCS 106 determining that a relatively high temperature isdetected by two or more RSD 108 in the same region of the facility 100,the FSCS 106 may send an alert 140 to all of the RSDs 108 currentlylocated in the region and/or sound an alarm and/or flash warning lightsin the region. The FSCS 106 may monitor responses to the alert 140,including how it is categorized by response personnel. This can includea response indicating whether the conditions were valid (e.g., not afalse alarm), and whether the alert 140 was of a correct priority, toolow of a priority or too high of a priority. Such a response may beprovided by safety personnel that reviews the safety incidents. If theFSCS 106 determines that a threshold number of responses to the currentalert 140 for a given set of conditions is not of the correct priority(e.g., too high or too low), the FSCS 106 may re-categorize the set ofconditions in a different risk category. For example, if a “too high”threshold is set to five consecutive instances, the second set ofconditions are encountered five times, resulting in five correspondingrelatively moderate priority regional alerts 140, and all five of thealerts 140 have a response of “too high”, then the FSCS 106 mayre-categorize the second set of conditions as low risk. Accordingly, thenext time the FSCS 106 identifies the second set of conditions, the FSCS106 may issue a relatively low priority local alert 140 (e.g., sendingan alert 140 to only the RSDs 108 that detected the relatively hightemperature). As a further example, if a “too low” threshold is set to1, the second set of conditions are encountered one time, resulting in acorresponding relatively moderate priority regional alert 140, and thealert 140 has a response of “too low”, then the FSCS 106 mayre-categorize the second set of conditions as high risk. Accordingly,the next time the FSCS 106 identifies the second set of conditions, theFSCS 106 may issue a relatively high priority plant-wide alert 140(e.g., sending an alert 140 to all of the RSDs 108 located in thefacility 100 and/or sounding an alarm and/or flashing warning lightsacross the entire facility 100).

FIG. 6 is a block diagram that illustrates a method 600 of dynamicallycategorizing conditions based on responses to corresponding alerts 140.The method 600 may be executed, for example, by the processing unit 130of the FSCS 106. In some embodiments, method 600 includes monitoringfacility safety data (block 602). This can include the FSCS 106collecting safety data 128 from one or more RSD 108 and/or one or moresensing device located throughout the facility 100, processing thesafety data 128 to determine current conditions in the facility 100, andcomparing the current conditions to a predefined listing of alertconditions to determine whether one more alert conditions exists (block604), such as a relatively high temperature detected by two or more RSDs108 in the same region of the facility 100. In response to determiningthat one more alert conditions exists, the FSCS 106 may proceed togenerating an alert (block 606) and monitoring to determine whether aresponse to the alert is received (block 608). This can includegenerating a relatively moderate priority regional alert 140 thatincludes sending an alert 140 to all of the RSDs 108 currently locatedin the region in which the two or more RSD 108 detected the relativelyhigh temperature, for presentation by the RSDs 108, and/or sounding analarm and/or flashing warning lights in the region, as well asmonitoring any responses to the alert 140, including how the alert 140is categorized by response personnel. In response to the FSCS 106receiving a response (e.g., from facility safety personnel) indicatingthat the alert is “too low” of a priority for the associated conditions(block 610), the FSCS 106 may proceed to increment to a “too low” count(e.g., adding 1 to the current value of the too low count for thecombination of the set of conditions including a relatively hightemperature detected by two or more RSDs in the same region of thefacility and the moderate priority regional alert) (block 612), andcompare the resulting too low count to a “too low count” threshold(e.g., a predefined low count threshold of 1 for the combination of theset of conditions including a relatively high temperature detected bytwo or more RSDs in the same region of the facility and the moderatepriority regional alert) (block 614). If the low count threshold issatisfied (e.g., the too low count is equal to or greater than 1), thenthe FSCS 106 may increase the condition risk category (block 616), suchas re-categorizing the second set of conditions (e.g., a relatively hightemperature detected by two or more RSDs in the same region of thefacility) into a high risk category associated with a relatively highpriority plant-wide alert 140, such as sending an alert 140 to all ofthe RSDs 108 located in the facility 100 and/or sounding an alarm and/orflashing warning lights across the entire facility 100. In response tothe FSCS 106 receiving a response is indicating that the alert is “toohigh” of a priority for the associated conditions (block 618), the FSCS106 may proceed to increment the “too high” count (e.g., adding 1 to thecurrent value of the too high count for the combination of the set ofconditions including a relatively high temperature detected by two ormore RSDs in the same region of the facility and the moderate priorityregional alert) (block 620), and compare the resulting too high count toa “too high count” threshold (e.g., a predefined high count threshold of5 for the combination of the set of conditions including a relativelyhigh temperature detected by two or more RSDs in the same region of thefacility and the moderate priority regional alert) (bock 622). If thetoo high count threshold is satisfied (e.g., the too high count is equalto or greater than 5), then the FSCS 106 may decrease the condition riskcategory (block 624), such as re-categorizing the second set ofconditions into a low risk category associated with a relatively lowpriority local alert 140, such as sending an alert 140 to only RSDs 108that detect a relatively high temperature. In response to determiningthat a response is received that does not indicate the alert is too highor too low (e.g., receiving a response indicating that the issued alert140 is of the correct priority or otherwise appropriate) (block 608, 610and 618), increasing a condition risk category (block 616) or decreasinga condition risk category (block 624), the FSCS 106 may proceed to setthe too high count to zero (block 626). In response to determining thata response is not received (block 608), determining that the too highcount threshold is not satisfied (block 622), or setting the too highcount to zero (block 626) the FSCS 106 may return to monitoring thefacility safety data (block 602). Such an embodiment can help to ensurethat sets of conditions are provided with an alert that corresponds totheir associated level of risk.

In some embodiments, zones of interest within the facility 100 aredynamically modified. For example, the FSCS 106 may obtain informationregarding the physical layout of the facility (e.g., including thelocation of pressure vessels containing gas in Areas 3 and 6, and thelocation of turbomachinery in Areas 4 and 7), and the FSCS 106 maygenerate different risk zones based on the layout of the facility (e.g.,a first “leak risk” zone that includes Areas 3 and 6, and a second“rotating hazard” zone that includes Areas 4 and 7). The zones may bedynamically modified based on characteristics of the zones and theenvironment. For example, if the FSCS 106 initially identifies the firstleak zone as including Areas 3 and 6 (but does not include Area 5 whichis located adjacent to and Southeast of Area 3), the FSCS 106 receivessafety data 128 from one or more RSDs 108, one or more sensing deviceslocated throughout the facility 100, and/or from an external weatherprovider, indicating a Northwest wind of 3 miles per hour in Area 3, theFSCS 106 determines that a gas leak in Area 3 is likely to spread intoArea 5 based on the wind speed and direction, then the FSCS 106 maydynamically add Area 5 to the first leak zone. In accordance withembodiments described herein, the updated zone can be used as a basisfor alerts 140. For example, if a leak is detected in Area 3 acorresponding alert 140 may include instructions to evacuate Areas 3, 5and 6, as well directions for navigating around potentially hazardousarea (e.g., “Move immediately to Area 1 by way of Area 2 and Area 4;Avoid Areas 3, 5 and 6”). In accordance with embodiments describedherein, the updated zones can be used as a basis for alerts 140 relatingto installation of required sensing modules 404. For example, if a RSD108 initially alerts a person 110 to install a temperature sensor module404 based on his/her work schedule indicating that he/she will beworking in Area 5 during his/her shift and/or based on the RSD 108 beinglocated in Area 5, in response to the Area 5 being added to the “leakzone” which requires use of a gas detection sensor module 404, anupdated alert 140 may generated and presented at the RSD 108, notifyingthe person 110 that they now need to install a gas detection sensormodule 404 Presentation of the alert 140 may include, for example, theRSD 108 displaying and/or audibly reciting the message “Based onchanging wind conditions, you are now required to install a gasdetection sensor module while located in Area 5” and/or illuminating ayellow flashing light and/or sounding a buzzer to indicate that arequired sensor module 404 (e.g., a gas detection sensor module 404) isnot installed in the RSD 108. The RSD 108 may continue to present thealert 140 until the RSD 108 detects that a gas detection sensor module404 has been installed in the RSD 108, the RSD 108 has moved out of theleak zone (e.g., the RSD 108 has moved out of out of Areas 3, 5 and 6),or the leak zone has been updated to no longer include the currentlocation of the RSD 108.

In some embodiments, monitoring of zones of interest is dynamicallyadjusted based on changing characteristics of the zone. For example, ifArea 5 is not initially included in a first “leak zone” identified asbeing susceptible to gas leaks, including Areas 3 and 6, then the FSCS106 may initially command the RSDs 108 of the facility 100 to operatetheir gas detection sensor modules 404 in a low-sensitivity while theyare located in the Area 5. In response to the FSCS 106 detecting asubsequent change in conditions indicating that Area 5 is nowsusceptible to gas leaks (e.g., the FSCS 106 detecting a Northwest windof 3 miles per hour in Area 3, and Area 5 being located Southeast ofArea 3 such that Area 5 is now susceptible to gas leaks), then the FSCS106 may add Area 5 to the first leak zone. The FSCS 106 may, then,command RSDs 108 of the facility 100 to operate their gas detectionsensor modules 404 in a high-sensitivity mode while they are located inthe first leak zone, including Area 5, and/or command RSDs 108 of thefacility 100 to operate their gas detection sensor modules 404 in alow-sensitivity while they are not located in the first region (oranother region susceptible to gas leaks).

FIG. 7 is a block diagram that illustrates a method 700 of dynamicallymodifying zones of interest within the facility 100 in accordance withone or more embodiments. The method 700 may be executed, for example, bythe processing unit 130 of the FSCS 106. In some embodiments, method 300includes monitoring facility safety data (block 702). This can includethe FSCS 106 collecting safety data 128 from one or more RSD 108 and/orone or more sensing devices located throughout the facility 100,processing the safety data 128 to determine current conditions in thefacility 100, and comparing the current conditions to prior conditionsto determine whether conditions have changed enough to warrant a changein the definition of one or more zones of interest (block 704), such asan increase in wind speed in Area 3, which is currently including withArea 6 is a first “leak zone” of interest, detected by wind gauges in oraround Area 3. In response to the FSCS 106 determining that conditionshave changed enough to warrant a change in the definition of one or morezones of interest, the FSCS 106 may proceed to updating the one or morezones of interest (block 706). For example, if the FSCS 106 initiallyidentifies the first leak zone as including Areas 3 and 6 (but does notinclude Area 5 which is located adjacent to an Southeast of Area 3), theFSCS 106 receives safety data 128 from one or more RSD 108 and/or one ormore sensing devices located throughout the facility 100 indicating aNorthwest wind of 3 miles per hour in Area 3, the FSCS 106 determinesthat a gas leak in Area 3 is likely to spread into Area 5 based on thewind speed and direction, then the FSCS 106 may dynamically add Area 5to the first leak zone. In response to updating a zone of interest, theFSCS 106 may determine whether any updated alerts need to be sent (block708), and may generate corresponding alerts (block 710). For example,with regard to installation of required sensing modules 404, if aninitial categorization of Area 5 requires RSDs 108 in Area 5 to installonly a temperature sensor module 404 while located in Area 5, inresponse to Area 5 being added to the “leak zone” (which requires use ofa gas detection sensor module 404 while located in Area 5), the FSCS 106may generate an updated alert 140 that is sent to RSDs 108 in Area 5,requiring the RSDs 108 to have a gas detection sensor module 404installed. In response to each of the RSDs in Area 5 receiving the alert140, each of the RSDs 108 may check to see if a gas detection sensormodule 404 is installed in the RSD 108, and if not the RSD 108 maypresent an alert 140 notifying the person 110 wearing the RSD 108 thatthey now need to install a gas detection sensor module 404. Presentationof the alert 140 may include, for example, the RSD 108 displaying and/oraudibly reciting the message “Based on changing wind conditions, you arenow required to install a gas detection sensor module while located inArea 5” and/or illuminating a yellow flashing light and/or sounding abuzzer to indicate that a required sensor module 404 (e.g., a gasdetection sensor module 404) is not installed in the RSD 108. The RSD108 may continue to present the alert 140 until the RSD 108 detects thata gas detection sensor module 404 has been installed in the RSD 108, theRSD 108 has moved out of the leak zone (e.g., the RSD 108 has moved outof out of Areas 3, 5 and 6), or the leak zone has been updated to nolonger include a current location of the RSD 108. As described herein,in response to detecting an alert condition, the FSCS 106 may issuesalerts 140 based on the updated zone of interest. For example, inresponse to the FSCS 106 detecting a leak in Area 3, a correspondingalert 140 may be issued to RSDs 108 in the facility 100, includinginstructions to evacuate Areas 3, 5 and 6, as well directions fornavigating around potentially hazardous area (e.g., “Move immediately toArea 1 by way of Area 2 and Area 4; Avoid Areas 3, 5 and 6”). The FSCS106 may also determine whether monitoring conditions need to be adjustedbased on the updated zone of interest (block 712), and, if so,configuring the RSDs 108 accordingly for the adjusted monitoring (block714). For example, in response to Area 5 being added to the first leakzone, the FSCS 106 may command the RSDs 108 in the facility 100 tooperate their gas detection sensor modules 404 in a high-sensitivitymode while they are located in any of Areas 3, 5 or 6, and/or commandthe RSDs 108 to operate their gas detection sensor modules 404 in alow-sensitivity while they are not located in the leak risk zone, oranother zone identified as being susceptible to gas leaks.

In some embodiments, alerts 140 are adapted based on the operationalstatus or other conditions of the facility 100. For example, if aportion of the facility 100 is operating normally, with operationalequipment 104 that is a potential safety hazard (e.g., rotatingequipment), then the FSCS 106 may issue an alert 140 to a RSD 108 inresponse to the FSCS 106 determining that the RSD 108 is approaching theequipment 104. If, however, the FSCS 106 determines that the facility100 is operating in a partial shut-down that includes the equipment 104being non-operational, such that the equipment 104 is not a potentialsafety hazard, then the FSCS 106 may not issue an alert 140 to a RSD 108in response to the FSCS 106 determining that the RSD 108 is approachingthe equipment 104. This can help to reduce false alarms and ensure thatpersons are provided with relevant alerts 140, reducing the likelihoodthe alerts 140 will be ignored. As a further example, in response to theFSCS 106 determining that the RSD 108 is approaching equipment 104 underun-safe conditions, such as the FSCS 106 determining that the RSD 108 isapproaching a ladder and a wind speed at or near the location of theladder is at or above a threshold level for ladder use, the FSCS 106 mayissue a corresponding alert 140 to a RSD 108 for presentation (e.g., theRSD 108 displaying or audibly reciting “Wind speed is too high forladder use”). If, however, the FSCS 106 determines that that the RSD 108is approaching equipment 104 under safe conditions, such as the FSCS 106determining that the RSD 108 is approaching the ladder and a wind speedat or near the location of the ladder is below a threshold level forladder use, then the FSCS 106 may not issue a corresponding alert 140 tothe RSD 108.

In some embodiments, alerts 104 are provided based on characteristics ofa person 110 and/or potential safety issues. For example, if the FSCS106 determines that a person 110 experiences a health issue when locatedin a particular region of the facility 100 and/or operating certaintypes of equipment 104, then the FSCS 106 may issue an alert 140 to aRSD 108 worn by the person 110, in response to determining that the RSD108 is approaching the region of the facility 100 and/or the type ofequipment 104. In some embodiments, the alert 140 includes a reminder ofpast experiences and a warning to use caution and/or a command to notproceed (e.g., the RSD 108 may display or recite audibly “You areapproaching Area 3. Please do not enter Area 3. In the past, you haveexperienced nausea after entering Area 3”). Similarly, if a secondperson 110 has similar health issues as the first person 110, the FSCS106 may determine that the other person 110 may be susceptible tosimilar risks, and issue a similar alert 140 to a RSD 108 worn by theother person 100 in response to the FSCS 106 determining that the RSD108 worn by the other person is approaching the portion of the facility100 and/or the type of equipment 104. Such an embodiment may help todeter persons from repeating or otherwise engaging in actions that havehistorically lead to safety issues.

FIG. 8 is a diagram that illustrates an example computer system (or“system”) 1000 in accordance with one or more embodiments. The system1000 may include a memory 1004, a processor 1006 and an input/output(I/O) interface 1008. The memory 1004 may include one or more ofnon-volatile memory (e.g., flash memory, read-only memory (ROM),programmable read-only memory (PROM), erasable programmable read-onlymemory (EPROM), electrically erasable programmable read-only memory(EEPROM)), volatile memory (for example, random access memory (RAM),static random access memory (SRAM), synchronous dynamic RAM (SDRAM)),and bulk storage memory (e.g., CD-ROM or DVD-ROM, hard drives). Thememory 1004 may include a non-transitory computer-readable storagemedium having program instructions 1010 stored thereon. The programinstructions 1010 may include program modules 1012 that are executableby a computer processor (e.g., the processor 1006) to cause thefunctional operations described, such as those described with regard tothe FSCS 106 and/or the RSDs 108.

The processor 1006 may be any suitable processor capable of executingprogram instructions. The processor 1006 may include a centralprocessing unit (CPU) that carries out program instructions (e.g., theprogram instructions of the program module(s) 1012) to perform thearithmetical, logical, and input/output operations described. Theprocessor 1006 may include one or more processors. The I/O interface1008 may provide an interface for communication with one or more I/Odevices 1014, such as external sensors, a computer mouse, a keyboard,speakers and a display screen (e.g., an electronic display fordisplaying a graphical user interface (GUI)). The I/O devices 1014 maybe connected to the I/O interface 1008 via a wired connection (e.g.,Industrial Ethernet connection) or a wireless connection (e.g., a Wi-Ficonnection). The I/O interface 1008 may provide an interface forcommunication with one or more external devices 1016, such as othercomputer devices and networks. In the context of a the computer system1016 being that of an RSD 108, the external devices 1016 may includeother RSDs 108 and/or the FSCS 106. In the context of a the computersystem 1000 being that of the FSCS 106, the external devices 1016 mayinclude the RSDs 108, external entities, and/or other sensing deviceslocated throughout the facility 100.

Further modifications and alternative embodiments of various aspects ofthe disclosure will be apparent to those skilled in the art in view ofthis description. Accordingly, this description is to be construed asillustrative only and is for the purpose of teaching those skilled inthe art the general manner of carrying out the embodiments. It is to beunderstood that the forms of the embodiments shown and described hereinare to be taken as examples of embodiments. Elements and materials maybe substituted for those illustrated and described herein, parts andprocesses may be reversed or omitted, and certain features of theembodiments may be utilized independently, all as would be apparent toone skilled in the art after having the benefit of this description ofthe embodiments. Changes may be made in the elements described hereinwithout departing from the spirit and scope of the embodiments asdescribed in the following claims. Headings used herein are fororganizational purposes only and are not meant to be used to limit thescope of the description.

It will be appreciated that the processes and methods described hereinare example embodiments of processes and methods that may be employed inaccordance with the techniques described herein. The processes andmethods may be modified to facilitate variations of their implementationand use. The order of the processes and methods and the operationsprovided therein may be changed, and various elements may be added,reordered, combined, omitted, modified, etc. Portions of the processesand methods may be implemented in software, hardware, or a combinationthereof. Some or all of the portions of the processes and methods may beimplemented by one or more of the processors/modules/applicationsdescribed herein.

As used throughout this application, the word “may” is used in apermissive sense (i.e., meaning having the potential to), rather thanthe mandatory sense (i.e., meaning must). The words “include,”“including,” and “includes” mean including, but not limited to. As usedthroughout this application, the singular forms “a”, “an,” and “the”include plural referents unless the content clearly indicates otherwise.Thus, for example, reference to “an element” may include a combinationof two or more elements. As used throughout this application, the term“or” is used in an inclusive sense, unless indicated otherwise. That is,a description of an element including A or B may refer to the elementincluding one or both of A and B. As used throughout this application,the phrase “based on” does not limit the associated operation to beingsolely based on a particular item. Thus, for example, processing “basedon” data A may include processing based at least in part on data A andbased at least in part on data B, unless the content clearly indicatesotherwise. As used throughout this application, the term “from” does notlimit the associated operation to being directly from. Thus, forexample, receiving an item “from” an entity may include receiving anitem directly from the entity or indirectly from the entity (e.g., viaan intermediary entity). Unless specifically stated otherwise, asapparent from the discussion, it is appreciated that throughout thisspecification discussions utilizing terms such as “processing,”“computing,” “calculating,” “determining,” or the like refer to actionsor processes of a specific apparatus, such as a special purpose computeror a similar special purpose electronic processing/computing device. Inthe context of this specification, a special purpose computer or asimilar special purpose electronic processing/computing device iscapable of manipulating or transforming signals, typically representedas physical, electronic or magnetic quantities within memories,registers, or other information storage devices, transmission devices,or display devices of the special purpose computer or similar specialpurpose electronic processing/computing device.

What is claimed is:
 1. An industrial facility safety system, comprising:a plurality of remote sensing devices (RSDs) disposed throughout anindustrial facility; and a facility safety control system (FSCS)configured to: collect safety data from the plurality of RSDs; determinecurrent conditions of the industrial facility based on the safety datacollected; determine that an alert condition exists based on the currentconditions determined; identify a second level alert associated with thealert condition; generate the second level alert for presentation topersonnel in the industrial facility; monitor a response to presentationof the second level alert, the response indicating whether the secondlevel alert is too low of a priority, too high of a priority, or of anappropriate priority for the alert condition; in response to determiningthat the response indicates that the second level alert is too low of apriority for the alert condition: incrementing a too low countassociated with the alert condition and the second level alert;determining whether the too low count associated with the alertcondition and the second level alert exceeds a too low count threshold;and in response to determining that the too low count associated withthe alert condition and the second level alert exceeds the too low countthreshold, associating a third level alert with the alert condition, thethird level alert being of higher priority than the second level alert;and in response to determining that the response indicates that thesecond level alert is too high of a priority for the alert condition:incrementing a too high count associated with the alert condition andthe second level alert; determining whether the too high countassociated with the alert condition and the second level alert exceeds atoo high count threshold; in response to determining that the too highcount associated with the alert condition and the second level alertexceeds the too high count threshold, associating a first level alertwith the alert condition, the first level alert being of lower prioritythan the second level alert.
 2. The system of claim 1, wherein the FSCSis further configured to, in response to determining the responseindicates that the second level alert is of an appropriate priority forthe alert condition, set the too high count associated with the alertcondition and the second level alert to zero.
 3. The system of claim 1,wherein the FSCS is further configured to: collect second safety datafrom the plurality of RSDs; determine second current conditions of theindustrial facility based on the second safety data collected; determinethat the alert condition exists based on the second current conditionsdetermined; identify an alert currently associated with the alertcondition; and generate the alert currently associated with the alertcondition for presentation to personnel in the industrial facility. 4.The system of claim 3, wherein the alert currently associated with thealert condition comprises one of the first level alert, the second levelalert and the third level alert.
 5. The system of claim 1, wherein thefirst level alert comprises an alert configured to be presented by afirst subset of the plurality of RSDs that are associated with the alertcondition, the second level alert comprises an alert configured to bepresented in one or more regions of the industrial facility that areassociated with the alert condition, and the third level alert comprisesa facility wide alert configured to be presented in all regions of theindustrial facility.
 6. The system of claim 1, wherein the FSCS isfurther configured to: determine a zone of interest within theindustrial facility based on the current conditions of the industrialfacility; collect third safety data from the plurality of RSDs;determine third current conditions of the industrial facility based onthe third safety data collected; and adjust the zone of interest basedon the third current conditions of the industrial facility.
 7. Thesystem of claim 6, wherein the FSCS is further configured to: determinea sensor module associated with the adjusted zone of interest; determineone or more RSDs located in the adjusted zone of interest; and send, tothe one or more RSDs located in the adjusted zone of interest, an alertto install the sensor module in the one or more RSDs.
 8. The system ofclaim 6, wherein the FSCS is further configured to: determine a sensingstate associated with the adjusted zone of interest; determine one ormore RSDs located in the adjusted zone of interest; and command the oneor more RSDs located in the adjusted zone of interest to operate in thesensing state.
 9. A method of industrial facility safety monitoring,comprising: collecting, by a facility safety control system (FSCS),first safety data from a plurality of remote sensing devices (RSDs)disposed throughout an industrial facility; determining, by the FSCS,first current conditions of the industrial facility based on the safetydata collected; determining, by the FSCS, that an alert condition existsbased on the first current conditions determined; identifying, by theFSCS, a first alert associated with the alert condition; generating, bythe FSCS, the first alert for presentation to personnel in theindustrial facility; monitoring, by the FSCS, a response to presentationof the first alert, the response indicating whether the first alert istoo low of a priority, too high of a priority, or of an appropriatepriority for the alert condition; in response to the FSCS determiningthat the response indicates that the first alert is too high of apriority for the alert condition, the FSCS: incrementing a too highcount associated with the alert condition and the first alert;determining that the too high count associated with the alert conditionand the first alert exceeds a too high count threshold; in response todetermining that the too high count associated with the alert conditionand the first alert exceeds the too high count threshold, associating asecond alert with the alert condition, the second alert being of lowerpriority than the first alert.
 10. The method of claim 9, furthercomprising: collecting, by the FSCS, second safety data from theplurality of RSDs; determining, by the FSCS, second current conditionsof the industrial facility based on the second safety data collected;determining, by the FSCS, that the alert condition exists based on thesecond current conditions determined; identifying, by the FSCS, thesecond alert currently associated with the alert condition; andgenerating, by the FSCS, the second alert currently associated with thealert condition for presentation to the personnel in the industrialfacility.
 11. The method of claim 9, further comprising, collecting, bythe FSCS, third safety data from the plurality of RSDs; determining, bythe FSCS, third current conditions of the industrial facility based onthe third safety data collected; determining, by the FSCS, that thealert condition exists based on the third current conditions determined;identifying, by the FSCS, a third alert currently associated with thealert condition; generating, by the FSCS, the third alert currentlyassociated with the alert condition for presentation to the personnel inthe industrial facility; monitoring, by the FSCS, a response topresentation of the third alert, the response indicating whether thethird alert is too low of a priority, too high of a priority, or of anappropriate priority for the alert condition; in response to the FSCSdetermining that the response indicates that the third alert is too lowof a priority for the alert condition, the FSCS: incrementing a too lowcount associated with the alert condition and the third alert;determining that the too low count associated with the alert conditionand the third alert exceeds a too low count threshold; and in responseto determining that the too low count associated with the alertcondition and the third alert exceeds the too low count threshold,associating a fourth alert with the alert condition, the fourth alertbeing of higher priority than the third alert.
 12. The method of claim11, further comprising, collecting, by the FSCS, fourth safety data fromthe plurality of RSDs; determining, by the FSCS, fourth currentconditions of the industrial facility based on the fourth safety datacollected; determining, by the FSCS, that the alert condition existsbased on the fourth current conditions determined; identifying, by theFSCS, a fifth alert currently associated with the alert condition;generating, by the FSCS, the fifth alert currently associated with thealert condition for presentation to the personnel in the industrialfacility; monitoring, by the FSCS, a response to presentation of thefifth alert, the response indicating whether the fifth alert is too lowof a priority, too high of a priority, or of an appropriate priority forthe alert condition; and in response to the FSCS determining theresponse indicates that fifth alert is of an appropriate priority forthe alert condition, the FSCS setting a too high count associated withthe alert condition and the fifth alert to zero.
 13. The method of claim9, wherein the second alert comprises an alert presented by a firstsubset of the plurality of RSDs that are associated with the alertcondition, and the first alert comprises an alert presented in one ormore regions of the industrial facility that are associated with thealert condition or a facility wide alert presented in all regions of theindustrial facility.
 14. The method of claim 9, further comprising:determining, by the FSCS, a zone of interest within the industrialfacility based on the current conditions of the industrial facility;collecting, by the FSCS, fifth safety data from the plurality of RSDs;determining, by the FSCS, fifth current conditions of the industrialfacility based on the fifth safety data collected; and adjusting, by theFSCS, the zone of interest based on the fifth current conditions of theindustrial facility.
 15. The method of claim 14, further comprising:determining, by the FSCS, a sensor module associated with the adjustedzone of interest; determining, by the FSCS, one or more RSDs located inthe adjusted zone of interest; and sending, by the FSCS to the one ormore RSDs located in the adjusted zone of interest, an alert to installthe sensor module in the one or more RSDs.
 16. The method of claim 14,further comprising: determining, by the FSCS, a sensing state associatedwith the adjusted zone of interest; determining, by the FSCS, one ormore RSDs located in the adjusted zone of interest; and commanding, bythe FSCS, the one or more RSDs located in the adjusted zone of interestto operate in the sensing state.
 17. A non-transitory computer readablestorage medium comprising program instructions stored thereon that areexecutable by a processor to cause the following operations ofindustrial facility safety monitoring: collecting, by a facility safetycontrol system (FSCS), safety data from a plurality of remote sensingdevices (RSDs) disposed throughout an industrial facility; determining,by the FSCS, current conditions of the industrial facility based on thesafety data collected; determining, by the FSCS, that an alert conditionexists based on the current conditions determined; identifying, by theFSCS, a second level alert associated with the alert condition;generating, by the FSCS, the second level alert for presentation topersonnel in the industrial facility; monitoring, by the FSCS, aresponse to presentation of the second level alert, the responseindicating whether the second level alert is too low of a priority, toohigh of a priority, or of an appropriate priority for the alertcondition; in response to determining that the response indicates thatthe second level alert is too low of a priority for the alert condition:incrementing a too low count associated with the alert condition and thesecond level alert; determining whether the too low count associatedwith the alert condition and the second level alert exceeds a too lowcount threshold; and in response to determining that the too low countassociated with the alert condition and the second level alert exceedsthe too low count threshold, associating a third level alert with thealert condition, the third level alert being of higher priority than thesecond level alert; and in response to determining that the responseindicates that the second level alert is too high of a priority for thealert condition: incrementing a too high count associated with the alertcondition and the second level alert; determining whether the too highcount associated with the alert condition and the second level alertexceeds a too high count threshold; and in response to determining thatthe too high count associated with the alert condition and the secondlevel alert exceeds the too high count threshold, associating a firstlevel alert with the alert condition, the first level alert being oflower priority than the second level alert.
 18. The medium of claim 17,the operations further comprising: in response to determining theresponse indicates that the second level alert is of an appropriatepriority for the alert condition, set the too high count associated withthe alert condition and the second level alert to zero.
 19. The mediumof claim 17, the operations further comprising: collecting second safetydata from the plurality of RSDs; determining second current conditionsof the industrial facility based on the second safety data collected;determining that the alert condition exists based on the second currentconditions determined; identifying an alert currently associated withthe alert condition; and generating the alert currently associated withthe alert condition for presentation to personnel in the industrialfacility.
 20. The medium of claim 19, wherein the alert currentlyassociated with the alert condition comprises one of the first levelalert, the second level alert and the third level alert.
 21. The mediumof claim 17, wherein the first level alert comprises an alert configuredto be presented by a first subset of the plurality of RSDs that areassociated with the alert condition, the second level alert comprises analert configured to be presented in one or more regions of theindustrial facility that are associated with the alert condition, andthe third level alert comprises a facility wide alert configured to bepresented in all regions of the industrial facility.
 22. The medium ofclaim 17, the operations further comprising: determining a zone ofinterest within the industrial facility based on the current conditionsof the industrial facility; collecting third safety data from theplurality of RSDs; determining third current conditions of theindustrial facility based on the third safety data collected; andadjusting the zone of interest based on the second current conditions ofthe industrial facility.
 23. The medium of claim 22, the operationsfurther comprising: determining a sensor module associated with theadjusted zone of interest; determining one or more RSDs located in theadjusted zone of interest; and sending, to the one or more RSDs locatedin the adjusted zone of interest, an alert to install the sensor modulein the one or more RSDs.
 24. The medium of claim 22, the operationsfurther comprising: determining a sensing state associated with theadjusted zone of interest; determining one or more RSDs located in theadjusted zone of interest; and commanding the one or more RSDs locatedin the adjusted zone of interest to operate in the sensing state.